QGIS Native Windows Build - GRASS Support Added

Today Freddy (Godofredo Contreras) and I hacked around a bit more on the Windows native build of QGIS. I've set up the build system to build both debug and release versions of QGIS at the same time. The idea is that users wishing to assist in the bug resolution process can run the debug versions and provide more detailed feedback provided by Dr Mingw crash reports, the console output (only present in the debug version) and, for the geekier folks out there, by using gdb to step through the code and provide stacktraces.

So I've made binary and release version snapshot setup packages and they are available for immediate download from http://qgis.org/uploadfiles/testbuilds/. These are not official preview release builds, just snapshot builds. If anyone out there wants to help it would be really good if you could download them and try out Radim's GRASS stuff (I'm clutching my lucky rabbits foot firmly as I say this). Id be particulary interested if anyone wants to try known grass issues from the previous win builds with this win build.

Next Freddy and I are getting Postgis integration to build and work. After that the GPS plugins is the last hurdle and then we shoud be ready to make a preview3 release of 0.8.

Thanks again to Freddy for all his help - its so great when people come along and pitch in.

test report QGIS win32 bins + GRASS plugin

I just tried the GRASS plugin with this new win binary version. These are my observations:

1. Startup time for QGIS seems to be signficantly smaller.
2. Opening a mapset thru the GRASS plugin works, but raster maps cannot be aded to the list of layers (vector maps seem to be working fine). They simply don't show up. Real showstopper, unfortunately·
3. Starting a GRASS shell via the GRASS toolbox only works, if (a) the msys directory is copied from Radim's set of files to the install dir and (b) QGIS has not been installed in a path that contains spaces (still the same problem as with Radim's version).

Minor things:

1. You can select "English" at the install prompt but the app itself will run with the localized GUI on a non-English Windows PC.
2. Uninstalling via the Windows Software managemer leaves the GRASS stuff and the install dir around.

Hope this helps.

Best,

Benjamin

test report

Just as with Benjamin, as long as there is no access to raster, and thus to the GRASS toolbox, it's not really worth for me to continue testing.

Vector seems to work fine. Display of a GRASS vector seems to be slower than the equivalent shape file.

Moritz

Minor thing: localization

Hi Benjamin,
only short explanation about language choose: the language in QGIS is automatically set from Windows regional settings. For QGIS installlation we use NSIS script in which isn't possible to determine Windows Regional settings . So there are 3 choices how to resolve this:

  1. prompt user to choose language for installation process;
  2. To use "English" only;
  3. Find out how to determine language from Windows registry.

For now the first is used.

Lubos