Support LIB_DIR_NAME environment variable for custom mapniklibpath #64
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As reported in Debian Bug #803564 and issue #62, the hardcoded
mapniklibpath
inpaths.py
is not correct when mapnik has been built using a customLIB_DIR_NAME
.The mapnik Debian package is built using
LIB_DIR_NAME=/mapnik/3.0
for which this change adds support insetup.py
for the python-mapnik build. It's quite similar to thefontscollectionpath
change from #59.Instead of, or in addition to, supporting custom paths using environment variables, may be
mapnik-config
should be used to retrieve the paths and fallback to the environment variables and hardcoded paths when unavailable.build.py
uses theMAPNIK_LIB_DIR
environment variable to set the path formapniklibpath
inpaths.py
, that's also an option instead of specifying only part of the path withLIB_DIR_NAME
.