[WIP] Support Launching NativeActivity with user-compiled library #1803
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
Author
|
This update will not meet Android 29 SDK requirements. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Original discussion: termux/termux-packages#2217
This PR brings the feature to termux that users can build and run own android app on their devices with following command:
am start -n com.termux/android.app.NativeActivity --es DYLIB_PATH $HOME/libmyapp.sotermux-app/AndroidManifest.xml
Exposes the NativeActivity that loads libnative-entrypoint.so
native-entrypoint/libnative-entrypoint.so
Loads shared library path from Intent "DYLIB_PATH", and try to call "ANativeActivity_onCreate" in specified shared lib.
Others