[Insight-users] Using ITK with visual studio and not cmake

[Luis Ibanez]

Hi Mark,


On Mon, Oct 19, 2009 at 12:56 PM, Mark Roden <mmroden at gmail.com> wrote:
> Let me put it this way: the CMake paradigm adopted by itk, that of
> single files to accomplish a simple task, is fine for little command
> line applications, but not how I want to build an application.  If I
> wanted to incorporate other libraries (ie, QT for useful interfaces,
> etc), trying to mesh these libraries with those will be most likely
> excruciating.
-----------------------------------------------------------------------------

On the contrary,

It is in the scenario of very large projects with many components
that you will notice the advantages of CMake.

It is not an accident that KDE adopted CMake as a configuration
system. We are talking about building 4.0 million lines of code.   :-)
http://www.kde.org/whatiskde/project.php

(that, yes, include dependencies on Qt libraries among many others).
For comparison, the Linux Kernel has 3.7 million lines of code.



>
> Maybe I don't understand CMake.  Frankly, I really don't want to.  I
> just want to use the libraries as libraries, not as a coding style or
> as a way to organize files.
>

and that's fine, we are all for Freedom.   :-)

However, you must be careful not to rationalize your lack of motivation
for learning about CMake, under the disguise of unfounded technical
arguments.


"I don't want to use CMake" if a perfectly valid argument in itself.
You can still use ITK, and simply will have to add more directories
to the little text boxes that Visual Studio provides for that purpose.


But, should you decide to discus the technical merits of CMake, you may
have to actually go through the effort of learning about it and comparing
it with alternative options.



       Regards,


            Luis