Differences

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

--- doc:appunti:prog:kivy_debian_12_android_11 [2024/11/20 15:39] – [Using the new venv install method] niccolo
+++ doc:appunti:prog:kivy_debian_12_android_11 [2024/11/21 09:55] (current) – [Prepare the Kivy project in user space] niccolo
@@ Line 78: / Line 78: @@
 ==== Using the new venv install method ====
-**NOTICE**: Till now we did not used this new preferred method, because the package **python-for-android** uses the old ''pip install'' method. See below about the //user method// install.
+:!: **WARNING**: Till now we did not use this new preferred method, because the package **python-for-android** uses the old ''pip install'' method. See below about the //[[#installation_in_user_space|user method]]// install.
 Instead of disabling the externally-managed-environment flag or instead of using the pip3 ''%%--user%%'' install method, it should be possible to use the venv pip3 install method. You need to install the **python3-venv** Debian package. This recipe did not work for me, but should be investigated further:
@@ Line 123: / Line 123: @@
 ==== Prepare the Kivy project in user space ====
+:!: **INFO**: This procedure is **required only once** when we start a new projec.
 Now it is time to prepare the Kivy project directory for the build of the Android package. You must check the following:
@@ Line 212: / Line 214: @@
 ==== Compiling the package (debug or release) ====
+:!: **INFO**: This is **the only procedure** to be executed whenever you want to compile a new version; the **version number** must be updated into the **main.py** source code.
 Enter the project directory and edit the **main.py** source code updating the definition of the **%%__version__%%** variable (the **buildozer.spec** will refer this value to create the package name). Then choose to make a debug build: