diff options
| author | Matthias Melcher <fltk@matthiasm.com> | 2018-03-02 16:07:23 +0000 |
|---|---|---|
| committer | Matthias Melcher <fltk@matthiasm.com> | 2018-03-02 16:07:23 +0000 |
| commit | f01eb0ec25d88451bb36c7ba070d60213b3cb8b3 (patch) | |
| tree | a2a40e8f73169f7a82befc9567dcc5980670fc87 /Android/README.txt | |
| parent | 5c2d98a5fcfdafe2e214a27a92876759cf0caea8 (diff) | |
Removing obsolete Android stuff
git-svn-id: file:///fltk/svn/fltk/branches/branch-1.4@12693 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
Diffstat (limited to 'Android/README.txt')
| -rw-r--r-- | Android/README.txt | 25 |
1 files changed, 0 insertions, 25 deletions
diff --git a/Android/README.txt b/Android/README.txt deleted file mode 100644 index 9f56e75a8..000000000 --- a/Android/README.txt +++ /dev/null @@ -1,25 +0,0 @@ - -here's the general process for building and installing an Android application which uses the NDK. - -1. cd to the root of its source code. - -2. Run ndk-build. This builds the native code, and should result in some .so files being put into the libs directory. - -3. android update project --path . --name something - -4. ant debug (or similar). This will build the Java code and create an .apk. Crucially, the build process will pick up the .so files left within the libs directory and include them into the .apk. - -5. adb install bin/name-of-project.apk - -6. Then launch as normal using the Android GUI or using an am start command such as you give. -6a. emulator -avd Intel_x86 - -7. adb shell am start -n com.example.native_activity - - or - - adb shell am start com.example.native_activity/android.app.NativeActivity - -8. adb uninstall com.example.native_activity - - - - Matt - |