[osgeo4w-dev] Proposing OrfeoToolbox integration in OSGeo4W

Julien Malik julien.malik at c-s.fr
Wed Oct 19 04:34:09 EDT 2011

Hi Frank,

> Julien,
> It sounds like you are in good shape for OSGeo4W integration

Good news !

>   and
> careful repackaging of your ZIP as a .tar.bz file,

I read that on the packaging instructions, just could not call the 
necessary tool from the python script which generates the package, so I 
used 7z to make a ZIP.
I'll dig further.

> possibly with some
> post install or initialization scripts should be all that is needed.

 From what I understand post install scripts are used to generate 
standalone launchers that can be run from the desktop or start menu, 
which is not needed here. Please correct me if I'm wrong.

Some environment vars are configured in an etc/ini bat file, so 
everything is ready to use from an OSGeo shell, or from desktop 
applications loading the osgeo4w env.
So I guess the content of the zip package we provide should be really 
close to the final result.

I understand I should move the python module part inside 
apps/python25/site-package instead of apps/orfeotoolbox/python + setting 
up the PYTHONPATH, but as efforts are being made towards python 27 
migration, maybe its ok like this (everything isolated in 
apps/orfeotoolbox) for the moment and I'll put it at the right place 
once python 27 will be on.

>   I would
> be happy to assist in any way I can to make this happen.  For instance
> arranging access to upload the package to the server, advice on
> packaging, etc.

That would be much appreciated !

My first question would be :
Is there a recommended procedure to test the installation process of a 
new package locally ?

I'm hanging out on IRC (#osgeo, #otb) so ping me when you have a few 
minutes to give.
I will definitely use some help !

> Packaging instructions are available at:
>    http://trac.osgeo.org/osgeo4w/wiki/PackagingInstructions
> It sounds like the OrfeoToolbox is a "soft" dependency for QGIS.
> That is, QGIS can take advantage of it if present, but does not require
> it.  Hopefully this means we don't need to make Orfeo a declared
> dependency of QGIS.

The Qgis package has no reason to depend on the OTB package.
Moreover, the OTB Python module has no dependency on Qgis.

Best regards,

More information about the osgeo4w-dev mailing list