Michael Hufer wrote:
We use cygwin, but that should be mostly the same:
-- cmd.exe (or in our case cygwin bash)
<set the variables so you can execute cl.exe from the cmd/bash shell>
$ set CC=cl.exe
$ set CXX=cl.exe
$ cmakesetup
---
in cmake setup: select build mode Unix Makefiles
and build mode (Debug or Release)
configure and create makefile(s)
---
$ cd build/dir
$ gmake install
---
Michael.
PS: For some reason a multible thread build (e.g. "gmake -j2 install") does
not work properly on Windows. It seems either gmake or the Visual Studio .NET
2003 compiler or linker is producing rubish if more than one is invoked
simultanously ;-(.
This works with VS 2005, or if you change the debug mode in VS 2003 to
not use pdb files.
This is what I use most of the time.
Also Cygwin broke make to not work with windows paths which cl uses:
http://public.kitware.com/pipermail/cmake/2006-August/010617.html
There is a fixed make here:
http://www.cmake.org/files/cygwin/make.exe
-Bill
_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake
