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