[cmake-developers] add_custom_command differences in tests

[Steve Wilson]

I have my topic branch with the add_custom_command changes to include the CONFIG keyword working.    The CMake binary produced from the build will correctly generated build systems that have custom commands with the CONFIG keyword.   I’m having trouble writing tests for the changes though.   When I run add_custom_command with the CONFIG keyword in the test suite the CONFIG keyword does not work.

I need a little guidance with the test suite.   I’m not super familiar with CTest so I’m not sure where to look next to find the problem.   So my question:  Why would add_custom_command behave differently in the tests than in regular build system generation?

Thank for any help.

SteveW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 236 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20140206/224d5d83/attachment-0001.sig>