Differences

This shows you the differences between two versions of the page.

--- doc:appunti:prog:kivy_debian_12_android_11 [2025/12/01 11:32] – [Upgrading the build tools (Android SDK)] niccolo
+++ doc:appunti:prog:kivy_debian_12_android_11 [2025/12/01 11:57] (current) – [Kivy version] niccolo
@@ Line 274: / Line 274: @@
 ==== Buildozer version ====
-To check **Buildozer version** installed:
+To check what version of Buildozer is installed:
 <code>
 buildozer --version
+</code>
+You can also ask pip3, using whatever //venv// or //user// variant you used:
+<code>
+pip3 list --user
+Package         Version
+--------------- -------
+buildozer       1.5.0
+...
+</code>
+The upgrade should be as simple as running
+<code>
 pip3 install --user --upgrade buildozer
 </code>
@@ Line 299: / Line 314: @@
 .01.21
 </code>
+Upgrading Buildozer will eventually upgrade also the python-for-android version. That **Android dependencies** will be stored inside the project subdirectory **$HOME/openolyimageshare/buildozer/android/platform/python-for-android**.
+You may want to require a specific python-for-android version by declaring the **p4a.branch** option into the **buildozer.spec** file:
+<file>
+# Use the default version:
+#p4a.branch = master
+# Use a specific p4a version:
+#p4a.branch = v2024.03.12
+# Use the develop version:
+#p4a.branch = develop
+</file>
+Remember to refresh the build environment with the ''buildozer android clean'' command.
 ==== Android SDK version ====
-Update the the **Android dependencies** inside the project subdirectory **$HOME/openolyimageshare/buildozer/android/platform/python-for-android**:
+All the SDKs downloaded will be stored into **$HOME/.buildozer/android/platform/android-sdk/platforms/** and are available to compile a package for the user.
+The SDK used to compile a specific package depends upon the **android.api** option you declared into the **buildozer.spec** file.
 <code>
@@ Line 312: / Line 344: @@
 </code>
-The above command **does not update Buildozer** nor **python-for-android**, but it downloads the **new Android SDK/API** into your **$HOME/.buildozer/** hierarchy (not into the project directory).
+The above command **does not update Buildozer** nor **python-for-android**, but it eventually downloads the **new Android SDK/API** into your **$HOME/.buildozer/** hierarchy (not into the project directory).
+==== Kivy version ====
+Usually you just declare that you need Kivy to compile the project by including it into the **requirements** of **buildozer.spec**:
+<file>
+requirements = python3,kivy,requests,android
+</file>
+You may be version specific with the syntax:
+<file>
+requirements = python3,kivy==2.3.0,requests,android
+</file>
+To inspect what version of Kivy was used in building the package, look into the prokect directory: **.buildozer/android/platform/build-arm64-v8a_armeabi-v7a/packages/kivy/**; you will find a file e.g. **2.3.0.zip**.
-==== Recompile with the new versions ====
+==== Recompile with the updated components ====
 Once you updated some components, be sure to clean the build environment: