[cmake-developers] cmake-2.8.5 build error on the MinGW/MSYS/wine platform

[Bill Hoffman]

On 9/15/2011 1:28 PM, Alan W. Irwin wrote:
> On 2011-09-15 09:27-0400 Bill Hoffman wrote:
>
>> On 9/15/2011 4:12 AM, Alan W. Irwin wrote:
>>
>>>
>>>>> That automatic installer (available
>>>>> at http://sourceforge.net/projects/mingw/files/Automated MinGW
>>>>> Installer/mingw-get-inst/)
>>>>> literally takes about 5 minutes to download and install all of
>>>>> MinGW/MSYS on wine, and I am sure that it would even be faster
>>>>> on Windows. Is there anybody game to try the build
>>>>> of cmake on Windows using the latest MinGW/MSYS stack you
>>>>> install with the automatic installer?
>>>
>> I just built with the most recent MinGW makefile build, and it works.
>
> "MinGW Makefiles" is quite different than the "MSYS Makefiles" builds
> I am doing. Also, note my comments to Brad about what constitutes the
> latest MinGW/MSYS. I am pretty sure from Brad's "MSYS Makefiles"
> result that all is well with "MSYS Makefiles" builds of CMake on
> Microsoft Windows, but being absolutely sure is even better than
> "pretty sure" which is why I asked him to try replicating exactly the
> same MinGW/MSYS install steps that I did.
>
>> Also, we have dashboards that do mingw and msys. See these builds:
>>
>> amber12.kitware Win32-mingw-gcc-4.5
>> amber12.kitware Win32-msys-gcc-4.5
>
> For the msys one you appear to be referring to
> http://www.cdash.org/CDash/iphone/buildsummary.php?buildid=1039633.

>
> There is no identification there of the exact MinGW/MSYS being used
> for that build. Furthermore, the cmake time is 6 seconds and the
> build time is 0 seconds (same start and end time). So it appears to be
> an update of a previous build rather than a build from scratch. That
> makes sense from the perspective of saving a lot of computer time on
> the machine doing the build, but it is not the same as the build from
> scratch that I am doing here. Again, it is the difference between
> being "pretty sure" and absolutely sure there is no trouble
> with "MSYS Makefiles" builds of CMake on Microsoft windows.
>
That is the wrong build tree.  We do a mingw and msys nightly builds 
that clean both the binary tree completely each night:

mingw:
http://www.cdash.org/CDash/buildSummary.php?buildid=1532357

msys:
http://www.cdash.org/CDash/buildSummary.php?buildid=1532166

>>
>
> I have avoided this step because I have been frankly intimidated by
> the size and complexity of the CMake code and my lack of (free)
> Windows platform knowledge. However, now you have encouraged me to
> try debugging it, I realize there is an even easier way to track down
> what is going on with the macros in question. That is, find the exact
> g++ command that failed from the VERBOSE=1 ouput, then repeat that by
> hand using the g++ -E -dD (or -dM) options.
>
> More later after I give that idea a try.

Sounds good, since you are the only one seeing the problem, you would be 
the best to figure it out.  It really is working on windows mingw and msys.

-Bill