Quoting Martin Apel <[EMAIL PROTECTED]>:
I got the impression, that the CMake generator for Visual Studio 7
ignores the working directory set in ADD_CUSTOM_COMMAND. Is this a bug
or is this a documented feature somehow?
Or am I simply doing something wrong?
Incidentally, I'm suffering this sam
Martin Apel wrote:
> WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR}
For VS this is the default working directory if no WORKING_DIRECTORY is
given.
> This calls a perl script to generate a bunch of Fortran files as needed.
> This script has to run in the output directory. I have c
Hi Bill
I simply do the following:
ADD_CUSTOM_COMMAND(OUTPUT ${FSrcWithBinDir}
${CMAKE_CURRENT_BINARY_DIR}/accessor_protos.h
COMMAND ${CMAKE_COMMAND} -E copy_if_different
${CMAKE_CURRENT_SOURCE_DIR}/FortranModules.inp
${CMAKE_CURRENT_BINARY_DIR}/FortranModules.inp
Martin Apel wrote:
Hi all,
I got the impression, that the CMake generator for Visual Studio 7
ignores the working directory set in ADD_CUSTOM_COMMAND. Is this a bug
or is this a documented feature somehow?
Or am I simply doing something wrong?
Might be a bug, might be you. Please provide a
Hi all,
I got the impression, that the CMake generator for Visual Studio 7
ignores the working directory set in ADD_CUSTOM_COMMAND. Is this a bug
or is this a documented feature somehow?
Or am I simply doing something wrong?
Regards,
Martin
Virus checked by G DATA AntiVirus
Ve
