OSGeo4W

Introduction

This page discusses the OSGeo Binary Distribution (OSGeo4W) and Installer of software for MS Windows. It is a specific case of the OSGeo Binary Distribution.

Comminication / Coordination

Mailing list: osgeo4w-dev@lists.osgeo.org (Subscribe, Archive)

Bugs: Create Ticket, Open Tickets

Goals

• Include a wide variety of OSGeo packages.
• Painless installation
• Select desired packages only, and pull in dependencies automatically.
• Focused on Win32 (NT/XP/Vista) with limited support for Win64.

Targetted Packages

In the following context committed means we are planning to include this item, and have someone willing to do the work. desired implies we are interested in including it, but no one is committed to doing it.

• MapServer (committed, Jeff)
  • MapServer CGI (committed, Jeff)
  • PHP MapScript (committed, Jeff)
  • Python MapScript (desired)
  • Perl Mapscript (desired)
• GDAL (committed, Mateusz)
  • Python bindings (desired)
  • Perl bindings (committed, Ari)
  • Plugin Drivers: ECW, OCI, SDE, MrSID, etc (desired)
• PostGIS/Postgres (desired) (Mark Cave-Ayland?)
• pgAdminIII/phppgadmin (desired)
• Mapbender (committed, Astrid)
• Mapbuilder (desired)
• OpenLayers (desired)
• WinGRASS (desired) (Moritz Lennert?) (Tcl/Tk)
• Qt (desired) (for OSSIM, and QGIS)
• QuantumGIS (desired) - depends on Qt.
• OSSIM (desired) - depends on Qt.
• R (desired)
• FDO (desired)
• MapGuide Open Source (desired) - depends on FDO
• Geoinformatica stack (contains GTK, Perl, GDAL, GDAL-Perl, GTK-Perl, etc) (committed, Ari)

More detailed information on specific packages is available on the OSGeo4W Packages wiki page.

Participants

(interested package maintainers please add your name below!)

• Jeff McKenna: MS4W Maintainer
• Frank Warmerdam: FWTools
• Mateusz Loskot: maintain GDAL related components
• Yewondwossen Assefa: MapServer core
• Ari Jolma: Geoinformatica stack
• Tamas Szekeres: GDAL C#, MapScript C#, Win64 packages
• Astrid Emde: Mapbender

Status

• a Cygwin Setup derived network installer has been selected for use, though it will be modified for a simplified expressed install: (working prototype)
• A preliminary pass has been made on a variety of OSGeo4W Packages. Some will need revision and many more will need to be added based on OSGeo4W Packaging.

Plans

• Hoping to have a reasonable stable "OSGeo4W 2008" ready for wide use by May 2008.
• select a Project Steering Committee
• longer term: enter incubation as an OSGeo project

Build Environment

Each package is build individually on the packagers machine, and then uploaded. There is no need for complete consistency in development environments. So packages might be built with MSVC 6, 7.1, 8, 9, MSYS/MingW and possibly even other compilers. Mixing compilers may be problematic for C++ interfaces, but is generally fine for C interfaces.

Packages used as libraries by other packages should have include files, and stub libraries in the package so the OSGeo4W tree can be used as a "buildkit" for additional packages.

Versions

• must pick our supported version of Java, perl, PHP, Python, etc. to use throughout installer buildkit