[CMake] Running NMake from a Cygwin Bash shell... is it possible?

[Miguel A. Figueroa-Villanueva]

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?

--Miguel

>
> HTH
> -Mathieu
>
> On 8/6/07, Miguel A. Figueroa-Villanueva wrote:
> > Hello everyone,
> >
> > Does anyone generate NMake makefiles and spawns the build from a
> > cygwin bash shell. If I generate Visual Studio 8 project files, then I
> > can use the following:
> >
> > devenv8.com CMake.sln /build Release /project ALL_BUILD
> >
> > from cygwin bash shell with no problems. But I can't manage to launch
> > the nmake makefiles from it. I can do it from a Dos shell, but not
> > bash. I do set the variables found in the vsvars32.bat as shown below.
> > I couldn't use the windows cmake to generate the NMake Makefiles, so I
> > tried generating the files from a Dos shell and then just using nmake
> > in the cygwin bash shell, but that didn't work either (ouput below).
> >
> > So, my question is.... does anybody manage to work this out or are the
> > tools just not compatible?
> >
> > Thanks,
> > --Miguel