GRASS & Postgres updates

New GRASS builds – 6.3 CVS weekly and 6.2 RC1. I also added a universal build of gpsbabel to the package so there is no need to download a separate GPSBabel app (I haven’t seen any that are universal yet). I don’t have much to test this on, so any feedback would be greatly appreciated.

Also, I removed Readline support from both GRASS and Postgres (the psql client app). This is for Panther compatibility. When I switched to the system’s libedit, I didn’t catch that Panther’s libedit isn’t fully readline-compatible. For me, the built-in history and editing capabilities on the Terminal are enough, but if there is interest I can take a look at adding readline back into GRASS and Postgres. At least in the future when I stop supporting Panther (when Leopard is released) I should be able to.

Just a couple more updates

PostGIS also broke with the GEOS framework change. New Postgres+PostGIS to fix that.

And, the weekly GRASS builds. GRASS 6.2 beta 3, and the weekend’s 6.3 CVS snapshot.

Oh, yeah, MacBook came back yesterday. Hopefully Apple truly figured out the RSS thing and I won’t have any more problems. Strangely, they replaced the hard drive. Most of yesterday was spent restoring from various backups and stuff I worked on on the PowerBook. ^_^

Framework updates

With the internal changes to the GDAL framework, I forgot to update the utility programs and the extra MrSID plugin. These are fixed now.

There is a similar problem with MapServer 4.8.4 and the GEOS framework (I made a small change I didn’t realize would affect dependent apps). I need to rebuild MapServer 4.8.4. The 4.10 beta is OK.

Framework updates

Mainly a change in the internals of GDAL – I decided to hide the included support libraries. Letting others link to the support libraries is a bit fragile, since they’re not guaranteed to stay there, or in the same form, and others who build their own GDAL framework (once it’s an option in the GDAL source) may not include them. This includes removing the Libraries symlink at the top level, unix/lib only has libgdal in it, and headers are only present for GDAL itself.

GDAL headers OK

GDAL headers are OK as ‘proper’ framework headers. It turns out no changes were needed. GDAL readme updated, no other changes to the framework.

Updates continue

Still getting by on the old PowerBook, sigh.

Just in time for FOSS4G! (sorry, I can’t make it) New MapServer 4.10 beta 3. Weekly GRASS 6.3 update from CVS, plus a small fix for a GUI issue.

I did some fine-tuning on the frameworks. This affects Xcode developers only. I have gone thru the frameworks to check that they work as proper frameworks with their headers – that is, frameworks don’t need -I includes flags to the compiler, and their headers can be included with <frameworkname/header.h>, such as #include <PROJ/proj_api.h> and CPP will find the header in /Library/Frameworks/PROJ.framework/Headers.

Many didn’t need any changes. A few needed some simple adjustments for this to work – FreeType, GEOS, Xerces and UnixImageIO. GDAL is the only one that needs more work, and does not have proper headers yet. The readmes of all frameworks have been updated to reflect this information, but only the 4 listed above had any changes made to the framework itself.

Limping along on the PB – some app updates

It’s sure easy to get spoiled. PowerBook – 1/5 the processing power = 5X build times. And I keep trying to scroll with the trackpad ^_^

A few updates today: GRASS 6.2b2 and the latest GRASS 6.3 CVS, and MapServer 4.10b2 (I was in the middle of the MS build when the RSS kicked in on the MacBook). Hopefully suddenly switching back to PPC won’t mess up the builds.

There is a new addition to the GRASS builds – a template for building addon modules without needing the full GRASS source. Similar to the GEM system, but it doesn’t need a lot of extra setup for the module source, and it lets you install the module where you want (and not in the app package, which is a Bad Thing for OS X apps). With this I enabled an Application Support folder in both the global Library and the user Library for installing addon modules. And the GRASS.app build source has also been updated to reflect this.

It’s kinda rough right now, and doesn’t support adding the modules to the GUI menus or a module registry (which require editing files in the app package, another Bad Thing). Changes in the GUI code are needed to handle an external menu config. Help files are not integrated in the main GRASS help pages.