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

Mark Roden mmroden at gmail.com
Mon Oct 19 15:00:58 EDT 2009


How about this:

Is there a way to include everything into a monolithic dll such that I
only need one header file instead of an entire tree?  There's already
just the option to build the library, and it puts everything into one
dll and many libs, but I still need to go through all of these hoops.

Mark

On Mon, Oct 19, 2009 at 10:54 AM, Xiaofeng Z <xf10036 at hotmail.com> wrote:
>
>        <3e0f01010910190956i1b56f320i44b7368a0a0d1790 at mail.gmail.com>
>
>
>  <B2DF102D-8C55-45B1-9E46-1156D7D78127 at bluequartz.net>
> Content-Type: text/plain; charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
> MIME-Version: 1.0
>
>
>
>
>>> Let me put it this way: the CMake paradigm adopted by itk=2C that of
>>> single files to accomplish a simple task=2C is fine for little command
>>> line applications=2C but not how I want to build an application. If I
>>> wanted to incorporate other libraries (ie=2C QT for useful interfaces=2C
>>> etc)=2C trying to mesh these libraries with those will be most likely
>>> excruciating. That's why I'm looking for a simple build location=2C
>>> with dlls=2C libs=2C and headers=2C not to incorporate with an entire co=
> ding
>>> paradigm.
> =20
> Much kudos to you for saying it!
> =20
> =20
>
>>
>> ITK uses the style of includes as "#include "itkImage.h" with out any
>> indication of what subfolder itkImage.h resides in. This means that
>> _every_ subfolder in the ITK installation/source needs to be
>> "included" in the compile command. This looks something like the
>> following (on OS X).
>>
>
> IMHO=2C this encourages bad programming habits.
> =20
>                                         =20
> _________________________________________________________________
> Your E-mail and More On-the-Go. Get Windows Live Hotmail Free.
> http://clk.atdmt.com/GBL/go/171222985/direct/01/=
>


More information about the Insight-users mailing list