Miguel A. Figueroa-Villanueva wrote:
On 8/6/07, Mathieu Malaterre wrote:
Hi Miguel,
I do that all the time. You only need to modify PATH to work on
cyginw (ie. replace the ; with :). You should NOT change LIB or
INCLUDE, those variable are read by cl/link thus should contains ; as
separators
This was the source of it all. You need PATH the way cygwin requires
(/cygdrive/c instead c: and colon separated list). For example,
cygVSINSTALLDIR="/c/Program Files/Microsoft Visual Studio 8"
...
export PATH="${cygVSINSTALLDIR}/Common7/Tools:<snip>:${PATH}"
But the LIB, LIBPATH and INCLUDE vars should maintain c: and semicolon
separated arguments, like in:
VCINSTALLDIR="c:/Program Files/Microsoft Visual Studio 8/VC"
export LIB="${VCINSTALLDIR}/ATLMFC/LIB;${VCINSTALLDIR}/lib;<snip>"
Thanks to Mathieu and Gonzalo for helping with this.
BTW, the mingw cmake does generate "NMake Makefiles" the cygwin cmake
doesn't. I successfully generated the "NMake Makefiles" with the mingw
cmake and built with nmake from the cygwin shell.
I think this is something worth noting in the Wiki... should I open a
FAQ entry or put it in the generator specific page?
I am not sure where it should go in the wiki, but it does seem to come
up a lot. The cygwin
cmake should only be used for building things with the cygwin tool
chain. The windows cmake
should be used for all other stuff on windows.
-Bill
_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
