Pygame's recipe updated to use latest libjpeg-turbo and libfreetype (optional for Python 2.7.11) #787
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
¡¡¡ Closed because currently I'm working with python's version 2.7.12, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR has the words "optional for Python 2.7.11" to keep reference to the original PR #775 (Python 2.7.11). This depends on PRs: #784, #785 and #793.
Here I force pygame to build against the p4a's libjpeg-turbo and p4a's libfreeetype instead of the ones distributed with the pygame_bootstrap_components. This way we avoid building all the stuff against different versions of libraries and the ones from the p4a are more updated. Unfortunately I cannot manage to use the same formula with libpng's recipe.
Merge note: Be careful with this because the
pygame_bootstrap_components/__init__.pyfile also has been modified in the Python 2.7.11 (PR #775) and it is possible that a merge conflict happens, if this is finally merged.