[Ctk-developers] VS2010 support
Sascha Zelzer
s.zelzer at dkfz-heidelberg.de
Wed Aug 3 14:56:33 UTC 2011
Yes, could be handy.
In each CMakeExternals/*.cmake script we could check for a CMake
variable <project_name>_REVISION_TAG and if it exists (i.e. manually
added in the CMake GUI or in a dart-client script) we use this one
instead of the default.
Does that make sense?
- Sascha
On 08/03/2011 04:44 PM, Julien Finet wrote:
> That sounds fine by me, however, I think we should have some way to
> optionally specify a custom tag ?
> So that we could have dashboards (on a next branch?) running with
> external bleeding edge branches.
>
> Julien.
>
> On Wed, Aug 3, 2011 at 3:41 AM, Sascha Zelzer
> <s.zelzer at dkfz-heidelberg.de <mailto:s.zelzer at dkfz-heidelberg.de>> wrote:
>
> Hi again,
>
> thanks to JC (who forwarded my post to the CMake mailing list) I
> could identify the problem (for details, see
> http://thread.gmane.org/gmane.comp.programming.tools.cmake.user/37472
> ).
>
> Essentially, supplying a GIT_TAG argument together with a
> UPDATE_COMMAND (could also be the default update command, which
> may be non-empty) in the ExternalProject_Add() macro call will
> skip all steps after the update step in Visual Studio 2010.
>
> This problem actually reveals some "issues" with our scripts in
> the CMakeExternals directory. I would like to suggest the following:
>
> 1.) Projects which are hosted on github/commontk
>
> I would prefer to keep GIT_TAG origin/patched or similar, but
> until the bug is fixed, we could specify a specific SHA1 value and
> add UPDATE_COMMAND ""
>
> This affects: CTKData, Log4Qt, PythonQt, QtSOAP, ZMQ (although
> hosted at github.com/patrickcheng/zmq2
> <http://github.com/patrickcheng/zmq2>)
>
> 2.) True external projects
>
> Here I would actually prefer GIT_TAG origin/tag where "tag" points
> to a release version. The relevant projects are:
>
> - DCMTK: we already use a fixed tag, just needs UPDATE_COMMAND ""
> - ITK: Use GIT_TAG v3.20.0
> - VTK: If I rember correctly, the CTK VTK widgets need a very
> recent VTK, so use a fixed SHA1 instead of origin/master
>
>
> I made these changes locally and successfully compiled CTK (I
> enabled everything without Python support) with VS2010 SP1.
>
> What do you think?
>
>
> Thanks,
> Sascha
>
>
>
> On 07/22/2011 06:07 PM, Sascha Zelzer wrote:
>
> Hi,
>
> there is something very strange going on. The generated VS
> 2010 projects
> (I am using the Express editions, 32bit) for the external
> dependencies
> like DCMTK, Log4Qt, etc. only call the download step of the
> ExternalProject_add call in our superbuild scripts. The
> projects are not
> configured and build.
>
> Did anybody experience the same? I tried with and without the
> VS 2010
> SP1 and with CMake 2.8.4 and 2.8.5.
>
> Thanks,
> Sascha
>
> On 07/22/2011 01:39 PM, Sascha Zelzer wrote:
>
> Hi Folks,
>
> I would like to get Visual Studio 2010 compatibility for CTK.
>
> Currently, it looks like I will have to copy
> ExternalProject.cmake to
> CTK for the CMAKE_CACHE_ARGS argument. Then a couple of small
> modifications should do.
>
> Any other ideas or objections?
>
> Thanks,
>
> Sascha
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at commontk.org
> <mailto:Ctk-developers at commontk.org>
> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at commontk.org <mailto:Ctk-developers at commontk.org>
> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>
>
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at commontk.org <mailto:Ctk-developers at commontk.org>
> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20110803/4661d8d1/attachment.htm>
More information about the Ctk-developers
mailing list