[CMake] VS.NET generation...
Lars Pechan
lars.pechan at parkerpechan.com
Wed Nov 10 15:10:34 EST 2004
Hi Brad,
sorry, still not entirely clear on this. If I use what you suggested
${EXEDIR}${CMAKE_CFG_INTDIR}/${CMDS}
I end up with file references looking like this:
Building Custom command D:/XXDev.nmake/exe./cmds.xml...
Now this actually does work but I think it looks a bit dodgy with the '.'
appended to the exe directory. From this I gather that CMAKE_CFG_INTDIR
evaluates to '.', not "/.". Otherwise I would have expected to see the
generated code as D:/XXDev.nmake/exe/./cmds.xml?
Can you please verify that this is indeed correct?
Thanks,
/Lars
----- Original Message -----
From: "Brad King" <brad.king at kitware.com>
To: "Lars Pechan" <lars.pechan at parkerpechan.com>
Cc: <cmake at www.cmake.org>
Sent: Thursday, November 11, 2004 12:45 AM
Subject: Re: [CMake] VS.NET generation...
> Lars Pechan wrote:
>> ADD_CUSTOM_COMMAND(
>> OUTPUT ${EXEDIR}/${CMAKE_CFG_INTDIR}/${cpFile}
>> COMMAND ${CMAKE_COMMAND}
>> ARGS -E copy ${GENDIR}/${cpFile}
>> ${EXEDIR}/${CMAKE_CFG_INTDIR}/${cpFile}
>> DEPENDS ${GENDIR}/${cpFile}
>> )
> [snip]
>> Is there a way I can explicitly set CMAKE_CFG_INTDIR in some carefully
>> chosen location to some other value than '\.' to see if that helps?
>
> The "proper" way to use CMAKE_CFG_INTDIR is like this:
>
> OUTPUT ${EXEDIR}${CMAKE_CFG_INTDIR}/${cpFile}
>
> Note the missing "/" character. It really evaluates to "/." or "/Debug",
> etc. so the slash will be added.
>
> -Brad
>
More information about the CMake
mailing list