-
Notifications
You must be signed in to change notification settings - Fork 93
Upgrade to PD 0.48 #70
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
Conversation
|
The Circle CI build is failing, however I think this is because I'm using my own fork for libpd. |
rpattabi
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
min sdk from 9 to 17 may be the only contention with this PR. Could we at least get it to 16? Jelly Bean is still alive unfortunately.
|
Regarding min version, building current master with NDK r15 emits a warning that our min version is effectively android-14: This change was introduced in NDK r15: |
- Raises min API level to 17 to make NDK build work NDK builds fail with API levels below 17. The reason is that https://github.com/pure-data/pure-data/blob/master/src/s_inter.c uses system calls 'munlockall' and 'mlockall' and these not defined for API levels 16 and below when building with NDK. - Adds PD 0.48 objects to PdTest patch
|
I've updated this PR and it is now based on the latest Regarding the issue of raising the minimum required Android SDK version from 14 to 17: As far as I understand, the options we have to avoid raising the min API level is to either:
I won't be able to explore these options, but if anyone else is interested please bring this up. I'd like to add that Android versions 14-16 are currently under 3% of all active Android devices according to Google and that it will still be possible to support these versions with pd-for-android version 1.0.2. pinging @joebowbeer for a second review and @nettoyeurny for any comments on the issue of raising the minimal Android API level. |
ea510a4 to
5a0dd9c
Compare
CircleCI NDK version is 10d. This change downloads NDK 15c and uses it instead
joebowbeer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm still hoping we can keep minSdkVersion at 14
circle.yml
Outdated
| @@ -5,7 +5,7 @@ machine: | |||
|
|
|||
| # Add ANDROID_NDK_HOME until CircleCI implements this requested feature. | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove obsolete comment
circle.yml
Outdated
| - echo y | android update sdk --no-ui --all --filter "tools" | ||
| - echo y | android update sdk --no-ui --all --filter "build-tools-26.0.2" | ||
| - yes | /usr/local/android-sdk-linux/tools/bin/sdkmanager --update --verbose | ||
| - wget https://dl.google.com/android/repository/android-ndk-r15c-linux-x86_64.zip; unzip android-ndk-r15c-linux-x86_64.zip: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per discussion below, ndk installation can be performed by sdk-manager?
https://discuss.circleci.com/t/licences-for-android-build-tools-not-accepted/17285/22
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but then I assume we'll get the latest NDK version, not a specific one.
Since NDK builds are often sensitive to the NDK version that is used, perhaps it's better to keep this as it is right now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With enough stars, perhaps CircleCI will provide this ready-made:
|
Does |
|
@joebowbeer latest commit also closes #78 |
|
Might also close #79 (needs to be tested) |
This pull request updates pd-for-android to the current libpd master branch which is based on PD 0.48.
The NDK build was initially failing for the following reasons which this PR solves:
The changes to Android.mk in the libpd repo should be merged first and then this PR could be updated to use the original libpd repo (instead of my own fork).
Pinging also @nettoyeurny : Perhaps you have a suggestion how raising the API level to 17 could be avoided?..