Thanks for the info guys but none of this really helps me out, especially the links to the CDash stuff. I don't even really know what I'm looking for.
What generator do I need to use when I run cmake in cygwin? Isn't that all I need? Won't CMake automatically pick up the MSVC compiler, even if it is inside Cygwin? I have MSVC 7.1, 8, and 9 on my system. The other thing I'm not sure of is how to tell CMake in Cygwin which MSVC compiler to use. If I need to setup environment variables, how do I know which ones CMake will be looking for and what the values should be? --------- Robert Dailey On Thu, Nov 10, 2011 at 3:26 PM, Bill Hoffman <bill.hoff...@kitware.com>wrote: > On 11/10/2011 3:12 PM, David Cole wrote: > >> This dashboard build of CMake is run from a cygwin bash script using >> gmake and the VS 2008 compiler: >> >> >> http://cdash.org/CDash/**buildSummary.php?buildid=**1711851<http://cdash.org/CDash/buildSummary.php?buildid=1711851> >> >> See the script that drives it here: >> >> >> http://cdash.org/CDash/**viewNotes.php?buildid=1711851<http://cdash.org/CDash/viewNotes.php?buildid=1711851> >> >> Perhaps there's a clue in there that will be useful/helpful. (There is >> also environment setup on that machine, though, too probably. Like all >> the stuff that vcvars.bat would set in a regular Windows cmd prompt.) >> >> > You will also need to use this gmake: > > > http://www.cmake.org/files/**cygwin/make.exe-cygwin1.7<http://www.cmake.org/files/cygwin/make.exe-cygwin1.7> > > > At some point support for paths with drive letters was removed from the > gmake that came with cygwin, so the makefiles do not work with stuff like > this: c:/path. The VS compiler needs that to work. There was a patch in > the upstream gmake and the above make has that patch. I have not tried > recently to see if cygwin updated make to work again. However, I use Unix > Makefiles with VS and gmake all the time, but I use the above gmake. > > To create the environment I started a vsvars.bat type shell, and dumped > the environment. I then convert that dump to a bash script. > > > Something like this: > > export INCLUDE='c:\Program Files ... > export LIB='c:\Program Files (x86)\Microsoft ... > export LIBPATH='c:\Windows\Microsoft.**NET\Framework ... > export PATH='/cygdrive/c/Program Files (x86)/Microsoft Visual Studio ... > export DevEnvDir='c:\Program Files ... > export VSINSTALLDIR='c:\Program Files (x86)\Microsoft Visual Studio 9.0' > export WindowsSdkDir='C:\Program Files\\Microsoft SDKs\Windows\v6.0A\' > export VCINSTALLDIR='c:\Program Files ... > export Framework35Version=v3.5 > export FrameworkDir='c:\Windows\**Microsoft.NET\Framework' > export FrameworkVersion=v2.0.50727 > > > -Bill > > > -- > > Powered by www.kitware.com > > Visit other Kitware open-source projects at http://www.kitware.com/** > opensource/opensource.html<http://www.kitware.com/opensource/opensource.html> > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/**CMake_FAQ<http://www.cmake.org/Wiki/CMake_FAQ> > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/**listinfo/cmake<http://www.cmake.org/mailman/listinfo/cmake> >
-- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake