8000 Fix broken --ndk-api default value · Pull Request #1484 · kivy/python-for-android · GitHub
[go: up one dir, main page]

Skip to content

Fix broken --ndk-api default value #1484

New issue 8000

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

Merged
merged 1 commit into from Nov 23, 2018
Merged

Fix broken --ndk-api default value #1484

merged 1 commit into from Nov 23, 2018

Conversation

ghost
Copy link
@ghost ghost commented Nov 23, 2018

I ran into this by accident while making the other pull requests. --ndk-api defaults to 0 in the parser, but code in other places (e.g. distribution.py) expects it to be None if not set. This breaks locating the proper final distribution in some cases when it's not specified, therefore I suggest this should be fixed.

@ghost
Copy link
Author
ghost commented Nov 23, 2018

There was no change with that force push, I just rebased onto latest master so I could locally pile up all the pull requests I currently depend on 😢

@inclement
Copy link
Member

#1472 provides a different fix that addresses the root cause better, but if this improves things then it seems fine to merge for now. Thanks.

@inclement inclement merged commit 80da6a3 into kivy:master Nov 23, 2018
@ghost ghost deleted the fixbrokenargdefault branch November 25, 2018 03:00
@DanShai
Copy link
DanShai commented Nov 26, 2018

When it was None I got tons of errors and couldnt build the apk, but @tshirtman solution worked like charm ! 0 is better and buit the apk on the fly. if you woried bout that line just replace:
if ndk_api is not None --to--> if ndk_api
thats it and leave it at 0

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
0