[Insight-developers] Building GaussianFilter Example
/MetaImageIO
Bill Hoffman
bill.hoffman@kitware.com
Fri, 27 Jul 2001 12:12:26 -0400
Since MetaImage is in the Unsupported directory, I don't think it should
be turned on like that. It could be with a similar use of variables
and the cache.
I think part of the problem is the Examples tree is a bit strange.
There is an Option build Examples, but once you turn that on, you
just get a new option for each individual Example. I think that
is a bit much. There should not be an option for each Example.
-Bill
At 12:00 PM 7/27/2001 -0400, Luis Ibanez wrote:
>Thanks for the instructions, the changes were made.
>
>However I was thinking more in the way RPM works:
>
>if you select on package, it will activate all the
>requirements too.
>
>That is, if I select to build GaussianFilter, it
>would be nice if MetaImage (previously marqued as
>a requirement) will be enabled during the CMake
>analysis of the CMakeList.txt files.
>
>Maybe it is just something for a wish list...
>
>
>Luis
>
>
>--------------
>
>
>Bill Hoffman wrote:
>>
>> The way to do it, is to check and make sure the library is built before
>> building the example, not the other way around.
>>
>> In the MetaImageIO library add this if it is built:
>> SET(HAS_METAIMAGE 1 CACHE INTERNAL "meta image support")
>>
>> If it is not built, then add this if it is not going to built
>> SET(HAS_METAIMAGE 0 CACHE INTERNAL "no meta image support")
>>
>> Then in the example:
>> IF(HAS_METAIMAGE)
>> ADD_TEST(itkGaussionFilter)
>> ...
>> ENDIF(HAS_METAIMAGE)
>>
>> -Bill
>>