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

Updates to configure pycairo if available #24

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

davenquinn
Copy link

The Mapnik core does not check to see if python cairo is importable as part of its
prebuild. Thus, the includes for pycairo (and the define HAVE_PYCAIRO) are not
part of the mapnik-config --cflags output. (In the Mapnik scons script, HAS_PYCAIRO=False
is set. This seems reasonable in general, if we are trying to separate python concerns
from the core software. But that means that there is no way to use pycairo from the python bindings if we want it. This adds a check to the setup to see if we can drag in pycairo.

@springmeyer
Copy link
Member

Thanks for working on this @davenquinn - definitely something that fell through the cracks in the split. Don't have the mindspace right now to review this method meaningfully but I will say that I wonder if we can rethink pycairo support such that it is not a compile time thing.

@davenquinn
Copy link
Author

Yeah, it might be reasonable to just remove the HAVE_PYCAIRO checks in src completely and rely on whether the mapnik build was configured with Cairo. It seems like that probably wouldn't break anything (and might provide better results for people using cairocffi instead of pycairo).

…into setup-updates

* 'master' of https://github.com/davenquinn/python-mapnik:
  Fix thread-local variables to use cross-platform Boost version
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.

2 participants