[Qgis-developer] Updating Win Build - stuck

[Alex Mandel]

Steve,

I'd be very interested in seeing any other notes you have on the
process. If you are building via MinGW and are willing to share in the
process I will be happy to help get your builds into the NSIS script to
create a new version of the Standalone installer.

My only goal here is a standalone installer with grass and python like
Macro used to make. It would be great if this didn't rely on a single
person as in the past so I would be very happy to collaborate with you.

FYI, I have access to virtual machines of most versions of windows for
building and testing but do not use windows myself(anymore).

Thanks,
Alex


S Mizuno wrote:
> Alex, 
> 
> I believe the problem is that qgssvnversion.h is not being constructed properly due to a test for MSVC in CMakeLists.txt in the top level source directory that should also test for MINGW , like in Python.cmake as you found. *nix commands are attempted, but fail since it is a Windows system.
> 
> see attached patch file
> 
> I hope this helps.
> 
> I have been using MinGW building for some time now and have some things I do to make compiling a little easier on my build system, which is somewhat different from the way Marco Pasetti documented Windows building. I would be willing to share these if you are interested. Most of these allow CMake to find libraries and headers without having to manually set the variables.
> 
> Steve
> 
> ---------- Original Message ----------
> From: Alex Mandel <tech_dev at wildintellect.com>
> To: qgis-developer <qgis-developer at lists.osgeo.org>
> Subject: [Qgis-developer] Updating Win Build - stuck
> Date: Sun, 08 Nov 2009 00:05:10 -0800
> 
> All,
> 
> I've been working on bringing the mingw/msys build back up to date with
> a working GRASS. So far via Marco's instructions and some shortcutting
> via OSGeo4w I think I'm getting close.
> 
> Ran into an error somewhere between 3-7%, see
> http://img8.imageshack.us/img8/232/cmakeerror.png
> 
> Based on ADKPete's suggestion I tried an mingw build of GEOS instead of
> osgeo4w but that didn't seem to change anything.
> 
> Oh and an FYI, Python.cmake should be changed to check for MINGW or MSVC
> for when to decide to use pyuic4.bat and pyrcc4.bat, or alternately just
> use WIN32. I manually hacked it with that for now, not 100% what the
> final solution is to ensure both build types with find the right python
> files in the cmakesetup.
> 
> Thanks,
> Alex