Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support LIB_DIR_NAME environment variable for custom mapniklibpath #64

Merged
merged 1 commit into from
Nov 27, 2015

Conversation

sebastic
Copy link
Contributor

As reported in Debian Bug #803564 and issue #62, the hardcoded mapniklibpath in paths.py is not correct when mapnik has been built using a custom LIB_DIR_NAME.

The mapnik Debian package is built using LIB_DIR_NAME=/mapnik/3.0 for which this change adds support in setup.py for the python-mapnik build. It's quite similar to the fontscollectionpath 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 the MAPNIK_LIB_DIR environment variable to set the path for mapniklibpath in paths.py, that's also an option instead of specifying only part of the path with LIB_DIR_NAME.

@sebastic
Copy link
Contributor Author

No comments on this?

@artemp
Copy link
Member

artemp commented Nov 27, 2015

@sebastic - looking good, I'm going to merge your PR.

@artemp artemp merged commit d14286e into mapnik:master Nov 27, 2015
@artemp
Copy link
Member

artemp commented Nov 27, 2015

@sebastic - thanks!

@sebastic sebastic deleted the mapnik-libdir branch November 27, 2015 10:56
@sebastic
Copy link
Contributor Author

Thanks for the merge!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants