Lines Matching refs:can
10 supported, but you can use the "android-project-ant" directory as a template.
37 The Android Java code implements an "Activity" and can be found in:
49 For simple projects you can use the script located at build-scripts/androidbuild.sh
67 If you want to create a signed release APK, you can use the project created by this
97 If you wish to use Android Studio, you can skip the last step.
102 Here's an explanation of the files in the Android project, so you can customize them:
109 …jni/Android.mk - Android makefile that can call recursively the Android.mk files in all subdirect…
168 directory will get bundled into the application package and you can load
204 app can continue to operate as it was.
207 where the GL context can not be restored. In that case you have to listen for
210 under iOS, if the OS can not restore your GL context it will just kill your app)
233 You can use STL in your project by creating an Application.mk file in the jni
259 You can see if adb can see any devices with the following command:
263 You can see the output of log messages on the default device with:
267 You can push files to the device with:
271 You can push files to the SD Card at /sdcard, for example:
275 You can see the files on the SD card with a shell command:
279 You can start a command shell on the default device with:
283 You can remove the library files of your project (and not the SDL lib files) with:
287 You can do a build with the following command:
291 You can see the complete command line that ndk-build is using by passing V=1 on the command line:
295 If your application crashes in native code, you can use ndk-stack to get a symbolic stack trace:
298 If you want to go through the process manually, you can use addr2line to convert the
313 You can see that there's a crash in the C library being called from the main code.
323 You can add logging to your code to help show what's happening:
329 If you need to build without optimization turned on, you can create a file called
350 Once valgrind is built, you can create a wrapper script to launch your
375 You can then launch your application normally and waaaaaaaiiittt for it.
376 You can monitor the startup process with the logcat command above, and
377 when it's done (or even while it's running) you can grab the valgrind
382 When you're done instrumenting with valgrind, you can disable the wrapper:
439 - Android OS can decide to terminate your application by calling onDestroy()
441 can handle to save things and quit.
445 NB: "Back button" can be handled as a SDL_KEYDOWN/UP events, with Keycode
453 is the current maximum number of buttons Android can report.