Maik Beckmann wrote:
Am Sonntag 18 Mai 2008 22:35:53 schrieb Stefan Buschmann:
Hi,
I don't know ifort, but I had the same problem with Makefiles and MSYS a
while ago.
Since it works with cygwin I assume ifort knows cygwin and handles the
forward slash right. Does anyone know if ifort has a flag or environment
variable name to set which tells ifort its working on windows.
There is nothing ifort could do about this. Every command line parameter
starting with a slash ('/') will be replaced by MSYS with the
corresponding windows path ('/foo/bar' will be translated to something
like 'C:\msys\foo\bar' I think). So the parameter will be translated
before ifort is even being executed. Since there is no way for MSYS to
know whether "/something" is a path that has to be translated or a
command line parameter, the only solution should be to use '-' instead
of '/'.
Stefan
Thank you very much Stefan!
A patch to fix Windows-ifort.cmake is attached.
Perhaps it is better to use a make that does not do this. mingw-make,
cygwin make, native win32 gmake. I am not sure you can completely avoid
/ type arguments in the entire tool chain for windows.
-Bill
_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
