[Insight-developers] [Insight-users] CMake config problem: ITK + GDCM 2 + VTK

Stephen Aylward stephen.aylward at kitware.com
Wed Jul 21 06:50:16 EDT 2010


Can't build MetaIO stand alone with this option.  Could be made to
work, but gets ugly.

Still waiting to hear about a var that indicates if building in ITK or VTK.

s

On Tue, Jul 20, 2010 at 11:13 PM, Mathieu Malaterre
<mathieu.malaterre at gmail.com> wrote:
> On Sun, Jul 18, 2010 at 7:34 PM, Karthik Krishnan
> <karthik.krishnan at kitware.com> wrote:
>> Hi Stephen:
>>
>> All I was suggesting was to move the lines :
>>
>>   set( METAIO_USE_NAMESPACE .. )
>>   set( METAIO_NAMESPACE .. )
>>   set( METAIO_LibrariesToLinkAgainst .. )
>>
>> over to the parent directory, where there is no need to check VTK_VERSION
>> etc, and then recurse into the MetaIO directory. Right now, there are switch
>> statements in the MetaIO CMakeLists.txt files stating "IF METAIO_FOR_ITK"
>> and "IF METAIO_FOR_VTK". The libraries in the Utilities folder, should not
>> need know that they are being built as a part of ITK or VTK.
>>
>> Others adopt the same strategy. For instance :
>>
>> (a) DICOMParser : The upper level CMakeLists.txt checks if sets the
>> variables : DICOMPARSER_NAMESPACE, DICOMPARSER_LIBRARY,
>> DICOMPARSER_STANDALONE  before recursing in
>>
>> (b) KWSys. Again, all the options, namespace names etc are set by the
>> toolkit in the parent directory..
>
> Clearly the best option AFAIK.
>
> Thanks karthik,
> --
> Mathieu
>



-- 

==============================
Stephen R. Aylward, Ph.D.
Director of Medical Imaging Research
Kitware, Inc. - North Carolina Office
http://www.kitware.com
stephen.aylward (Skype)
(919) 969-6990 x300


More information about the Insight-developers mailing list