[Insight-developers] Request for new target: ITKHeaderTests
Matthew McCormick (thewtex)
matt at mmmccormick.com
Sun Sep 4 18:56:42 EDT 2011
Another option may be to keep the current behavior, but add a custom
target that is not added to ALL, so the header tests can be
regenerated and built on request. I will work on a patch for this.
Thanks,
Matt
On Sun, Sep 4, 2011 at 6:22 PM, Matt McCormick
<matt.mccormick at kitware.com> wrote:
> Hi Bill,
>
> I think that is a good idea, but I am not sure how to implement it
> correctly.. Right now it regenerates the tests when CMake is run,
> even though that is an unusual way of doing things.
>
> I though about an add_custom_command, but it is difficult to specify
> the dependencies correctly. The test should be run when headers are
> new or moved around, which cannot be know apriori.
>
> If we do add_custom_target and add it to make all, it will build all
> the header tests on every make, which can be time consuming and
> annoying. But, if you still think this is the way to go or if you
> have other ideas, please let me know.
>
> Thanks,
> Matt
>
> On Sun, Sep 4, 2011 at 4:21 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
>> Matt,
>>
>> The ITK header tests are an excellent addition to our black-box testing. It
>> would be great if there was a target, perhaps called, ITKHeaderTests.
>>
>> We have a target ITKData which is very convenient.
>>
>> Having a new target for the header tests would avoid having to do a "make"
>> at the top level while debugging new modules.
>>
>> Bill
>>
>>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Kitware offers ITK Training Courses, for more information visit:
> http://kitware.com/products/protraining.html
>
> Please keep messages on-topic and check the ITK FAQ at:
> http://www.itk.org/Wiki/ITK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.itk.org/mailman/listinfo/insight-developers
>
More information about the Insight-developers
mailing list