Ticket #2371 (new defect)

Opened 2 months ago

Last modified 2 months ago

GDAL plugins path is not coherently managed in the building system: please avoid embedded paths.

Reported by: frankie Assigned to: warmerdam
Priority: normal Milestone:
Component: ConfigBuild Version: svn-trunk
Severity: normal Keywords:
Cc:

Description

It would be better introducing an --autoload=/custom/path for the plugins directory instead of embedding a fixed path as in the GDAL/OGR cores (currently /lib/gdalplugins). The GDAL_DRIVER_PATH/OGR_DRIVER_PATH environment variables can be retained as well, but apparenly thery are not documented out of the source code (if I'm not missing something).

This is the same approach used in the grass configuration script in frmts/grass and it would allow packager to customize without patching sources. Patching is required in order to have multiple paths for different cohexisting libraries.

Change History

05/14/08 18:03:18 changed by frankie

  • version changed from unspecified to svn-trunk.
  • component changed from default to ConfigBuild.

05/15/08 10:58:44 changed by frankie

The same considerations apply for <prefix>/share/gdal

06/03/08 17:49:08 changed by rouault

Francesco, any patch for that ?

As for the <prefix>/share/gdal, are you refering to INST_DATA ? This one is defined in GDALmakeopt.in as @datadir@, so I guess that ./configure --datadir=XXXXX should solve the issue (I haven't try though)