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

Remove hardcode references to MacOSX10.12.sdk #198

Closed
wants to merge 32 commits into from
Closed

Conversation

martinmiglio
Copy link

With reference to issue #167
In the mason-packages, there are hardcoded references to MacOSX10.12.sdk for the xcode sdks required to build mapnik._mapnik extension. If you install xcode on a mac today, the included SDK is MacOSX 10.14, which won't work for building python-mapnik because mason is looking for version 10.12. The new SDK isn't named MacOSX.sdk anymore, it is now called simply MacOSX.sdk thus versioned names aren't necessary.

artemp and others added 30 commits January 19, 2017 11:15
Signed-off-by: Asbjørn Sloth Tønnesen <[email protected]>
Now that printing isn't loaded automatically
it must be loaded explicitly.

Fixes: 4f7f090 An attempt to solve printing import error
Signed-off-by: Asbjørn Sloth Tønnesen <[email protected]>
  - The 3.0.13-1 package builds mapnik without a soname
  - This takes advantage of that by expecting a non-versioned, non-symlink library name on linux
  - This is important when packaging portable binaries to avoid copying only a symlink and leaving a broken install
Pin 3.0.x branch against Mapnik 3.0.x mason package
@talaj
Copy link
Member

talaj commented Nov 2, 2018

Thank you for the information. However, I don't see how merging v3.0.x branch into master can help with the issue.

Also it is not needed or desirable to use mason-packages for running python-mapnik. The only reason for mason-packages is to provide versions of dependencies under which visual tests are passing. This is not needed unless you want to participate in development of Mapnik.

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.

8 participants