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

Fix matplotlib and update to v3.1.3 #2076

Merged
merged 6 commits into from
Mar 5, 2020
Merged

Conversation

opacam
Copy link
Member

@opacam opacam commented Mar 1, 2020

This PR depends on a working kiwisolver and cppy recipes (#2075).

Closes: #1900, kivy/buildozer#1003

Notes: I will merge the branch of this PR alongside the branch of #2075 into #2073 so we can see if the thing is working with the on_device_unit_test_app.

See also:


Because, for unix platforms, the mpl install script uses `pkg-config`
to detect libraries installed in non standard locations (our case...
well...we don't event install the libraries...so we must trick a little
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we don't event -> we don't even

def get_install_requires(self):
- return ['numpy>=1.10.0']
- return ['numpy>=1.11']
+ return ['numpy==1.16.4'] # to match p4a's target version
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have some doubts with this line. Does it really have to be hard pinned to the current default p4a numpy version?
And if it does, should we at some point try to pick this up dynamically?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have some doubts with this line. Does it really have to be hard pinned to the current default p4a numpy version?

I'm not sure, I'm doing a local test...we will see

And if it does, should we at some point try to pick this up dynamically?

I think so, but it will add more complexity to the recipe...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes I was also thinking about the complexity. I think we can address that later if needed.
You have my ✔️ feel free to merge if it builds 💚

AndreMiras
AndreMiras previously approved these changes Mar 1, 2020
Copy link
Member

@AndreMiras AndreMiras left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, the Python 2 armeabi-v7a (with numpy) build failed on network IO, so I restarted

AndreMiras
AndreMiras previously approved these changes Mar 1, 2020
Copy link
Member

@AndreMiras AndreMiras left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM thanks

@opacam
Copy link
Member Author

opacam commented Mar 4, 2020

Thanks for the Approval @AndreMiras 😄

Note: I updated the first post, since with the changes made in here we can close some issues.

@opacam
Copy link
Member Author

opacam commented Mar 5, 2020

I think that this is ready to 🔀

let's do it!!

😸

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