More updates for GDAL issues

I rebundled GRASS 6.2.1 with the new non-Python-based startup wrapper, so there shouldn’t be random problems with Python environment corruption. I did NOT rebuild GRASS 6.2.1, so it still uses GDAL 1.3.

I forgot Qgis had bundled GRASS libs that still link to GDAL 1.3. I fixed this with a new binary. I also added a universal gpsbabel, with USB support, to the Qgis application package. Qgis should automatically find it, but I don’t have any GPS hardware to test it. The Xcode project has also been updated with the patch needed for Qgis to find gpsbabel in the app package, and to copy it into the bundle.

New GRASS 6.3 CVS binary and Xcode project to match. Up-to-date with today’s CVS. I renamed Run Script and Copy Files build phases in the Xcode project so it’s easier to follow the build logic.

New GDAL 1.4 build to fix CURL problems on Panther.

Multiple GDAL versions

It turns out that GDAL 1.4 framework is not as backward compatible as I had thought. It’s not GDAL’s fault, but the OSX’s fault. OSX versioning doesn’t work well across major versions. A compatibility version of 1 and current version of 2 don’t work reliably – a program built with an older version of the framework that has compat and current versions of 1 will complain about the newer framework being too old. Or I’m just missing something in my understanding of all this.

So, I changed GDAL to be the same compat and current versions, and the installer now retains 1.3 if it exists. This lets older software that uses GDAL 1.3 still work with 1.4 installed. Currently, this includes MapServer with old-style build (not framework build) and GRASS 6.2.1 in my packages.

There are instructions on the frameworks page for reinstalling both 1.3 and 1.4 (and a download link for 1.3).

A few updates

GRASS binary and Xcode project up-to-date for this weekend’s CVS.

UnixImageIO updated – PNG updated to 1.2.15.

Postgres updated to 8.2.1. PostGIS updated to 1.2.1.

PostGIS quick update

Somehow the new sql files for PostGIS 1.2 didn’t make it into the installer, the old 1.1 sql was still there. Corrected in r2 of Postgres 8.2 + PostGIS 1.2. There is also a separate download of just the sql files so you don’t need to download and install the whole Postgres package.

A Bunch of Updates

Tired brain, so here’s the short version:

SQLite3 framework 3.3.9

UnixImageIO framework 1.0.8 – New JasPer 1.900.0.

Postgres 8.2.0 + PostGIS 1.2.0 – I wrestled with making Xcode projects for these, but without complete success, so I figured I should get an update out before it got too old. Postgres is such an oddball build (it actually uses ld for linking in many places), that after figuring out how to get around one problem, another always came up. Arrgh! So, back to my split configure build and merge (for universal binaries). Note that this is a major upgrade to Postgres and PostGIS, see the upgrade readme for instructions.

GRASS.app 6.3 CVS 07-1-3 – fixes the GUI startup blocking CLI use, and a couple other script runtime issues.

New Year’s Update

Happy New Year!

Qgis 0.8.0 has been released. Includes Xcode project to match. Requires new GDAL framework. I will probably not do SVN builds now, just updates to the release.

I quietly updated GDAL just after Xmas – 1.4 beta. Internal version bump, but 1.4 is basically backward compatible with 1.3. New software builds, such as the Qgis 0.8 above, will not work on older GDAL 1.3 frameworks. But older software should continue to work with GDAL 1.4.

MapServer test

Xcode mania! I set up an xcode project for MapServer (not available yet), and in the process built a framework for the MapServer library, to replace the standard static library. This remove 2.3 MB from every (13) MapServer binary. This should be considered a beta release, but please test if you can.

QGIS + GRASS followup-date

I’ve brought the QGIS and GRASS Xcode projects up to date with yesterday’s binaries.

GRASS: Worked out a PPC build bug with the fonts (I hope). Fixed a couple typos. Made Postgres and FFTW support optional with a simple switch (plus a manual build of the PG drivers). Added easy build instructions for a universal TclTk X11 and universal GPSBabel.

QGIS: I used the xcconfig ideas from the GRASS Xcode project for this update. Much easier to configure. Also updated to use SVN source from 2006-12-20. I added a download for the source snapshot I used, to avoid possible source update problems, since Qgis doesn’t do periodic fixed snapshots.

QGIS + GRASS update

Fun stuff! Tackling some integration issues and other glitches. New GRASS 6.3 CVS and QGIS 0.8 SVN builds.

GRASS is mostly just a rebuild. Library paths are internally correct for a normal installation in /Applications/GRASS.app. This is to make Qgis happy.

QGIS is where the big changes are. First, fixed a broken Postgres plugin. Next, a catch-22 and general integration problem with GRASS. As it was, Qgis could read GRASS data directly and open GRASS mapsets for editing. But running GRASS commands would only work when Qgis was run from within a running GRASS session. If Qgis has a valid GISBASE for the GRASS plugin (as was the case with the bundled GRASS libraries), there is no way to force it to use another GRASS, such as a full GRASS installation.

But, even if you could choose another GISBASE, it still wouldn’t work, since the GRASS commands couldn’t find the GRASS libraries. Then there’s a little restriction in Mac OS X on navigating into application packages, so you can’t choose the GRASS.app package as the GISBASE.

So, I changed the bundled GRASS library base so that it is not seen as a valid GISBASE. Without GRASS.app, Qgis can now only view GRASS data directly. It cannot open mapsets, let alone run GRASS commands. To enable full GRASS support, install the GRASS.app from this update in the Applications folder (and NOT a subfolder or other location).

You must use this QGIS SVN application and this GRASS CVS application for this to work. GRASS.app must be directly in the Applications folder. That’s the way it is until something is worked out in QGIS. There are instructions in the Qgis readme how to do this.