<div class="gmail_quote">On Wed, Jul 21, 2010 at 4:20 PM, Stephen Aylward <span dir="ltr"><<a href="mailto:stephen.aylward@kitware.com">stephen.aylward@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Can't build MetaIO stand alone with this option. Could be made to<br>
work, but gets ugly.<br></blockquote><div><br>Why ? (I believe you can build DICOMParser and most utilities stand alone as well)<br><br>MetaIO/CMakeLists.txt would simply check if the few vars are not already defined and if so assign then.<br>
<br>if (NOT METAIO_NAMESPACE)<br> set( METAIO_NAMESPACE "..." )<br>endif(NOT METAIO_NAMESPACE)<br><br><br>This way, its can be used as a part of packages other than ITK and VTK and being built standalone as well, right ?<br>
<br>Thanks<br>--<br>karthik<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Still waiting to hear about a var that indicates if building in ITK or VTK.<br>
<br>
s<br>
<br>
On Tue, Jul 20, 2010 at 11:13 PM, Mathieu Malaterre<br>
<div class="im"><<a href="mailto:mathieu.malaterre@gmail.com">mathieu.malaterre@gmail.com</a>> wrote:<br>
</div><div><div></div><div class="h5">> On Sun, Jul 18, 2010 at 7:34 PM, Karthik Krishnan<br>
> <<a href="mailto:karthik.krishnan@kitware.com">karthik.krishnan@kitware.com</a>> wrote:<br>
>> Hi Stephen:<br>
>><br>
>> All I was suggesting was to move the lines :<br>
>><br>
>> set( METAIO_USE_NAMESPACE .. )<br>
>> set( METAIO_NAMESPACE .. )<br>
>> set( METAIO_LibrariesToLinkAgainst .. )<br>
>><br>
>> over to the parent directory, where there is no need to check VTK_VERSION<br>
>> etc, and then recurse into the MetaIO directory. Right now, there are switch<br>
>> statements in the MetaIO CMakeLists.txt files stating "IF METAIO_FOR_ITK"<br>
>> and "IF METAIO_FOR_VTK". The libraries in the Utilities folder, should not<br>
>> need know that they are being built as a part of ITK or VTK.<br>
>><br>
>> Others adopt the same strategy. For instance :<br>
>><br>
>> (a) DICOMParser : The upper level CMakeLists.txt checks if sets the<br>
>> variables : DICOMPARSER_NAMESPACE, DICOMPARSER_LIBRARY,<br>
>> DICOMPARSER_STANDALONE before recursing in<br>
>><br>
>> (b) KWSys. Again, all the options, namespace names etc are set by the<br>
>> toolkit in the parent directory..<br>
><br>
> Clearly the best option AFAIK.<br>
><br>
> Thanks karthik,<br>
> --<br>
> Mathieu<br>
><br>
<br>
<br>
<br>
</div></div>--<br>
<div><div></div><div class="h5"><br>
==============================<br>
Stephen R. Aylward, Ph.D.<br>
Director of Medical Imaging Research<br>
Kitware, Inc. - North Carolina Office<br>
<a href="http://www.kitware.com" target="_blank">http://www.kitware.com</a><br>
stephen.aylward (Skype)<br>
(919) 969-6990 x300<br>
</div></div></blockquote></div><br>