[cmake-developers] add_custom_command differences in tests

[Steve Wilson]

On Feb 6, 2014, at 10:12 PM, Ben Boeckel <ben.boeckel at kitware.com> wrote:

> On Thu, Feb 06, 2014 at 17:30:11 -0700, Steve Wilson wrote:
>> 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?
> 
> Hmm. Are you using your installed ctest or the build tree's ctest? If
> the former, it may be using your installed cmake.

I thought of that also, but my installed ctest/cmake has support for the CONFIG keyword (it’s a build from my private fork of the project, of which I’m trying to merge interesting changes back to the main project).


-------------- 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/20140207/2e2a001f/attachment-0002.sig>