[CMake] WORKING_DIRECTORY ignored for ADD_CUSTOM_COMMAND on VisualStudio?

[Martin Apel]

Hi Brad,

this is kind of difficult under Windows, as far as I know. I have MSys 
installed on my machine, but the pwd "command" is not really a command 
(i.e. .exe) under MSys, but a shell script, which invokes
the shell command "pwd". Windows sees the file with the "pwd" command in 
C:\MSys\bin as an ordinary file, not an executable. So I cannot call 
this from within ADD_CUSTOM_COMMAND. As I am no Windows expert, I 
haven't found any other way. Can you recommend a way, how to do this?

Regards,

Martin

Brad King wrote:
> 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 checked the
>> generated .vcproj file and it doesn't contain anything related to
>> the working directory for this command. I modified the command to use
>>                   COMMAND ${CMAKE_COMMAND} -E chdir ${PERL_EXECUTABLE}
>> ${CMAKE_SOURCE_DIR}/scripts/createFortAccessors.pl
>> and now it works properly. But still, my impression is, that the Visual
>> Studio generator ignores this parameter.
>>     
>
> Have you tried a custom command that just prints the working directory
> to see where it is?
>
> -Brad
>
>   


-- 

Martin Apel                                     Tel:     0049 8153 9288-47
Software Architect                              E-Mail:  martin.apel at simpack.de

INTEC GmbH                                      Tel:     0049 8153 9288-0
Argelsrieder Feld 13                            Fax:     0049 8153 9288-11
82234 Wessling                                  E-Mail:  intec at simpack.de
Germany                                         URL:     http://www.simpack.com


____________
Virus checked by G DATA AntiVirus
Version: AVKA 18.309 from 27.06.2008