Backport Android API 19 support #291
Open
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 monstrosity of a patchset reverts a bunch of libuv changes that dropped Android API 19 support in latest rebase. I am not sure how tight nodejs dependency on specific libuv version is, so maybe libuv version downgrade could somehow solve this in a more graceful manner.
On the other hand, API 19 is pretty much a dead platform nowadays, but since I've already committed into this (like I already did for nodejs-mobile 0.3.1, when patches only involved two files, but I forgot to test it and open a PR), let me just leave that here up for review.
So far I've only tested this on API 25 device (running aarch64, but with
ndk.abiFilter
set to justarmeabi-v7a
) and API 19 emulator and it seems to work.I'll try to test it on my proper API 19 target this week.I did some preliminary testing on my target physical platform and it seems to work fine so far. I'll undraft this PR after further testing.I've been using this in production on a bunch of API versions for a couple of months and didn't encounter any issues.Checklist