Sorry, I got lost in the course of the discussion. I was referring to
$CONFIGURATION. Thanks for the correction.
Petr
On Wed, Nov 7, 2012 at 12:52 PM, David Cole david.c...@kitware.com wrote:
Peter K: ${CMAKE_CFG_INTDIR} is NOT a generator expression, and it
does work in the output clause of
On second thought, CMAKE_CFG_INTDIR won't work for multi-configuration
generators. It is using $(OutDir) for Visual Studio 2008 generator,
which my custom command can't understand. I'd like to use
$CONFIGURATION but then it won't work for single-configuration
generators (like NMake) where I want
The multi-configuration generators do understand CMAKE_CFG_INTDIR.
CMake generates code to call your custom command, including $(OutDir)
wherever you reference ${CMAKE_CFG_INTDIR}, and then Visual Studio
sets that before invoking your command so that it gets resolved to the
correct
I was specifying that in my path for one of the OUTPUT files in
add_custom_command(). Is there any limitation on where/how it can be
used in a custom command?
On Tue, Nov 6, 2012 at 2:41 PM, David Cole david.c...@kitware.com wrote:
The multi-configuration generators do understand
Yes, there is a limitation. You can't use them in OUTPUT. See
http://public.kitware.com/Bug/view.php?id=12877
Petr
On Wed, Nov 7, 2012 at 12:26 AM, Robert Dailey rcdailey.li...@gmail.comwrote:
I was specifying that in my path for one of the OUTPUT files in
add_custom_command(). Is there any
I'm using a custom target to copy files to the following directory:
${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/$CONFIGURATION
This works on Visual Studio generators, because binaries that are
compiled are placed in the directory above.
However, if I generate for NMake on Windows, binaries are placed in
Sorry I got confused, what I needed to use is CMAKE_CFG_INTDIR.
On Mon, Nov 5, 2012 at 5:17 PM, Robert Dailey rcdailey.li...@gmail.com wrote:
I'm using a custom target to copy files to the following directory:
${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/$CONFIGURATION
This works on Visual Studio
