compiling_for_android.rst 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291
  1. .. _doc_compiling_for_android:
  2. Compiling for Android
  3. =====================
  4. .. highlight:: shell
  5. .. seealso::
  6. This page describes how to compile Android export template binaries from source.
  7. If you're looking to export your project to Android instead, read :ref:`doc_exporting_for_android`.
  8. Note
  9. ----
  10. In most cases, using the built-in deployer and export templates is good
  11. enough. Compiling the Android APK manually is mostly useful for custom
  12. builds or custom packages for the deployer.
  13. Also, you still need to follow the steps mentioned in the
  14. :ref:`doc_exporting_for_android` tutorial before attempting to build
  15. a custom export template.
  16. Requirements
  17. ------------
  18. For compiling under Windows, Linux or macOS, the following is required:
  19. - `Python 3.6+ <https://www.python.org/downloads/>`_.
  20. - `SCons 3.1.2+ <https://scons.org/pages/download.html>`_ build system.
  21. - `Android SDK <https://developer.android.com/studio/#command-tools>`_
  22. (command-line tools are sufficient).
  23. - Required SDK components will be automatically installed.
  24. - On Linux, **do not use an Android SDK provided by your distribution's repositories** as it will often be outdated.
  25. - On macOS, **do not use an Android SDK provided by Homebrew** as it will not be installed in a unified location.
  26. - Gradle (will be downloaded and installed automatically if missing).
  27. - JDK 17 (either OpenJDK or Oracle JDK).
  28. - You can download a build from `ojdkbuild <https://adoptium.net/temurin/releases/?variant=openjdk17>`_.
  29. .. seealso:: To get the Godot source code for compiling, see
  30. :ref:`doc_getting_source`.
  31. For a general overview of SCons usage for Godot, see
  32. :ref:`doc_introduction_to_the_buildsystem`.
  33. .. _doc_android_setting_up_the_buildsystem:
  34. Setting up the buildsystem
  35. --------------------------
  36. - Set the environment variable ``ANDROID_HOME`` to point to the Android
  37. SDK. If you downloaded the Android command-line tools, this would be
  38. the folder where you extracted the contents of the ZIP archive.
  39. - Windows: Press :kbd:`Windows + R`, type "control system",
  40. then click on **Advanced system settings** in the left pane,
  41. then click on **Environment variables** on the window that appears.
  42. - Linux or macOS: Add the text ``export ANDROID_HOME="/path/to/android-sdk"``
  43. to your ``.bashrc`` or ``.zshrc`` where ``/path/to/android-sdk`` points to
  44. the root of the SDK directories.
  45. - Install the necessary SDK components in this folder:
  46. - Accept the SDK component licenses by running the following command
  47. where ``android_sdk_path`` is the path to the Android SDK, then answering all the prompts with ``y``:
  48. ::
  49. cmdline-tools/latest/bin/sdkmanager --sdk_root=<android_sdk_path> --licenses
  50. - Complete setup by running the following command where ``android_sdk_path`` is the path to the Android SDK.
  51. ::
  52. cmdline-tools/latest/bin/sdkmanager --sdk_root=<android_sdk_path> "platform-tools" "build-tools;34.0.0" "platforms;android-34" "cmdline-tools;latest" "cmake;3.10.2.4988404" "ndk;23.2.8568313"
  53. - After setting up the SDK and environment variables, be sure to
  54. **restart your terminal** to apply the changes. If you are using
  55. an IDE with an integrated terminal, you need to restart the IDE.
  56. - Run ``scons platform=android``. If this fails, go back and check the steps.
  57. If you completed the setup correctly, the NDK will begin downloading.
  58. If you are trying to compile GDExtension, you need to first compile
  59. the engine to download the NDK, then you can compile GDExtension.
  60. Building the export templates
  61. -----------------------------
  62. Godot needs two export templates for Android: the optimized "release"
  63. template (``android_release.apk``) and the debug template (``android_debug.apk``).
  64. As Google requires all APKs to include ARMv8 (64-bit) libraries since August 2019,
  65. the commands below build an APK containing both ARMv7 and ARMv8 libraries.
  66. Compiling the standard export templates is done by calling SCons from the Godot
  67. root directory with the following arguments:
  68. - Release template (used when exporting with **Debugging Enabled** unchecked)
  69. ::
  70. scons platform=android target=template_release arch=arm32
  71. scons platform=android target=template_release arch=arm64 generate_apk=yes
  72. .. note::
  73. If you are changing the list of architectures you're building, remember to add
  74. ``generate_apk=yes`` to the *last* architecture you're building, so that an APK
  75. file is generated after the build.
  76. The resulting APK will be located at ``bin/android_release.apk``.
  77. - Debug template (used when exporting with **Debugging Enabled** checked)
  78. ::
  79. scons platform=android target=template_debug arch=arm32
  80. scons platform=android target=template_debug arch=arm64 generate_apk=yes
  81. The resulting APK will be located at ``bin/android_debug.apk``.
  82. .. seealso::
  83. If you want to enable Vulkan validation layers, see
  84. :ref:`Vulkan validation layers on Android <doc_vulkan_validation_layers_android>`.
  85. Adding support for x86 devices
  86. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  87. If you also want to include support for x86 and x86_64 devices, run the SCons
  88. command a third and fourth time with the ``arch=x86_32``, and
  89. ``arch=x86_64`` arguments before building the APK with Gradle. For
  90. example, for the release template:
  91. ::
  92. scons platform=android target=template_release arch=arm32
  93. scons platform=android target=template_release arch=arm64
  94. scons platform=android target=template_release arch=x86_32
  95. scons platform=android target=template_release arch=x86_64 generate_apk=yes
  96. This will create a fat binary that works on all platforms.
  97. The final APK size of exported projects will depend on the platforms you choose
  98. to support when exporting; in other words, unused platforms will be removed from
  99. the APK.
  100. Cleaning the generated export templates
  101. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  102. You can use the following commands to remove the generated export templates:
  103. ::
  104. cd platform/android/java
  105. # On Windows
  106. .\gradlew clean
  107. # On Linux and macOS
  108. ./gradlew clean
  109. Using the export templates
  110. --------------------------
  111. Godot needs release and debug APKs that were compiled against the same
  112. version/commit as the editor. If you are using official binaries
  113. for the editor, make sure to install the matching export templates,
  114. or build your own from the same version.
  115. When exporting your game, Godot opens the APK, changes a few things inside and
  116. adds your files.
  117. Installing the templates
  118. ~~~~~~~~~~~~~~~~~~~~~~~~
  119. The newly-compiled templates (``android_debug.apk``
  120. and ``android_release.apk``) must be copied to Godot's templates folder
  121. with their respective names. The templates folder can be located in:
  122. - Windows: ``%APPDATA%\Godot\export_templates\<version>\``
  123. - Linux: ``$HOME/.local/share/godot/export_templates/<version>/``
  124. - macOS: ``$HOME/Library/Application Support/Godot/export_templates/<version>/``
  125. ``<version>`` is of the form ``major.minor[.patch].status`` using values from
  126. ``version.py`` in your Godot source repository (e.g. ``4.1.3.stable`` or ``4.2.dev``).
  127. You also need to write this same version string to a ``version.txt`` file located
  128. next to your export templates.
  129. .. TODO: Move these paths to a common reference page
  130. However, if you are writing your custom modules or custom C++ code, you
  131. might instead want to configure your APKs as custom export templates
  132. here:
  133. .. image:: img/andtemplates.png
  134. You don't even need to copy them, you can just reference the resulting
  135. file in the ``bin\`` directory of your Godot source folder, so that the
  136. next time you build you will automatically have the custom templates
  137. referenced.
  138. Building the Godot editor
  139. -------------------------
  140. Compiling the editor is done by calling SCons from the Godot
  141. root directory with the following arguments:
  142. ::
  143. scons platform=android arch=arm32 production=yes target=editor
  144. scons platform=android arch=arm64 production=yes target=editor
  145. scons platform=android arch=x86_32 production=yes target=editor
  146. scons platform=android arch=x86_64 production=yes target=editor generate_apk=yes
  147. You can skip certain architectures depending on your target device to speed up
  148. compilation. Remember to add ``generate_apk=yes`` to the *last* architecture
  149. you're building, so that an APK file is generated after the build.
  150. The resulting APK will be located at ``bin/android_editor_builds/android_editor-release.apk``.
  151. Removing the Editor templates
  152. -----------------------------
  153. You can use the following commands to remove the generated editor templates:
  154. ::
  155. cd platform/android/java
  156. # On Windows
  157. .\gradlew clean
  158. # On Linux and macOS
  159. ./gradlew clean
  160. Installing the Godot editor
  161. ---------------------------
  162. With an Android device with Developer Options enabled, connect the Android device to your computer via its charging cable to a USB/USB-C port.
  163. Open up a Terminal/Command Prompt and run the following commands from the root directory with the following arguments:
  164. ::
  165. adb install ./bin/android_editor_builds/android_editor-release.apk
  166. Troubleshooting
  167. ---------------
  168. Platform doesn't appear in SCons
  169. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  170. Double-check that you've set the ``ANDROID_HOME``
  171. environment variable. This is required for the platform to appear in SCons'
  172. list of detected platforms.
  173. See :ref:`Setting up the buildsystem <doc_android_setting_up_the_buildsystem>`
  174. for more information.
  175. Application not installed
  176. ~~~~~~~~~~~~~~~~~~~~~~~~~
  177. Android might complain the application is not correctly installed.
  178. If so:
  179. - Check that the debug keystore is properly generated.
  180. - Check that the jarsigner executable is from JDK 8.
  181. If it still fails, open a command line and run `logcat <https://developer.android.com/studio/command-line/logcat>`_:
  182. ::
  183. adb logcat
  184. Then check the output while the application is installed;
  185. the error message should be presented there.
  186. Seek assistance if you can't figure it out.
  187. Application exits immediately
  188. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  189. If the application runs but exits immediately, this might be due to
  190. one of the following reasons:
  191. - Make sure to use export templates that match your editor version; if
  192. you use a new Godot version, you *have* to update the templates too.
  193. - ``libgodot_android.so`` is not in ``libs/<arch>/``
  194. where ``<arch>`` is the device's architecture.
  195. - The device's architecture does not match the exported one(s).
  196. Make sure your templates were built for that device's architecture,
  197. and that the export settings included support for that architecture.
  198. In any case, ``adb logcat`` should also show the cause of the error.