Alan wrote:

> Isn't that the complete issue?  My experience (under Wine, but the 
principle
> is the same) is you must have mingw32-make.exe on your
 PATH in order for -G
> "MinGW Makefiles" to work.  So you will 
have to be careful of dependencies,
> but you should be able to 
download and unpack mingw32-make.exe from the
> normal SF location
 for that (under mingw) while keeping the normal MinGW gcc
> 
compilers off your PATH (since you want to use the different compilers,
>
 MinGW-W32 and MinGW-W64).

I did not realize that cmake calls mingw32-make.exe, since the user has to call 
it explicitly after running cmake.  But I see now.  Cmake tries compiling as a 
part of finding the compilation tools.

Your suggestion worked, for both W32 and W64.  I used -G "MinGW Makefiles" for 
both cases.

This also works with CMake 2.8 stable/release version.  So I still cannot 
figure what's new in RC2 with respect to MinGW-W64.  Since it works, there is 
no issue really.

Just like CMake is able to distinguish different versions of Visual Studio, 
would it distinguish MinGW-32 with MinGW-64 also (which means either both would 
be in path simultaneously, or neither would be, and cmake picks the right one 
based on the generator specifed)?  Let me know if so, and I'll be happy to test 
this.

I have already reported missing mingw32-make.exe to MinGW-W64.

Best regards - Alok

---------------------------------------------------------------
> Date: Wed, 16 Jun 2010 19:32:32 -0700
> From: ir...@beluga.phys.uvic.ca
> To: alokgo...@hotmail.com
> CC: david.c...@kitware.com; cmake@cmake.org
> Subject: Re: [CMake] CMake 2.8.2-rc2 ready for testing!
> 
> On 2010-06-16 19:04-0700 Alok Govil wrote:
> 
> > Hi all,
> > 
> > I am unable to build using MinGW-W64, but chances are there would be some
> > configuration issues.
> > 
> > Here is how I am setup right now:
> > 
> > 1.  Download latest "automatic" builds (W64 and W32) from here: 
> > http://mingw-w64.sourceforge.net/
> > 2.  Removed prefixes:  For example, renamed file
> > "x86_64-w64-mingw32-g++.exe" in the bin folder to "g++.exe".  Am I not
> > supposed to do this anymore?
> > 3.  Added CMake 2.8.2 RC2 as well as "one" of W64 and W32 to the path.
> > 4.  cmake . -G "MinGW Makefiles"      // This could be wrong for W64, but
> > fails for even W32.
> >      This step is where I get various errors from CMake.  It works fine with
> > normal MinGW.
> > 5.  Then I usually call "mingw32-make" but that is not even there in
> > MinGW-W32 and MinGW-W64!!
> 
> Isn't that the complete issue?  My experience (under Wine, but the principle
> is the same) is you must have mingw32-make.exe on your PATH in order for -G
> "MinGW Makefiles" to work.  So you will have to be careful of dependencies,
> but you should be able to download and unpack mingw32-make.exe from the
> normal SF location for that (under mingw) while keeping the normal MinGW gcc
> compilers off your PATH (since you want to use the different compilers,
> MinGW-W32 and MinGW-W64).
> 
> Alan
> __________________________
> Alan W. Irwin
> 
> Astronomical research affiliation with Department of Physics and Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
> 
> Programming affiliations with the FreeEOS equation-of-state implementation
> for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
> package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
> Linux Links project (loll.sf.net); and the Linux Brochure Project
> (lbproject.sf.net).
> __________________________
> 
> Linux-powered Science
> __________________________
                                          
_________________________________________________________________
Hotmail is redefining busy with tools for the New Busy. Get more from your 
inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2
_______________________________________________
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

Reply via email to