doc:appunti:prog:kivy_debian_12_android_11
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
doc:appunti:prog:kivy_debian_12_android_11 [2024/04/02 07:58] – [Compiling the package] niccolo | doc:appunti:prog:kivy_debian_12_android_11 [2024/04/04 07:08] – [Writing the buildozer.spec file] niccolo | ||
---|---|---|---|
Line 181: | Line 181: | ||
You can use **presplash.filename** and **icon.filename** to include two artwork in your app. The // | You can use **presplash.filename** and **icon.filename** to include two artwork in your app. The // | ||
- | In **android.permissions** you must list all the permissions that your app will require from the operating system. If you forget to declare something your app simply will not be able to do that operation. Beware that starting from Android 10 the access to the external | + | In **android.permissions** you must list all the permissions that your app will require from the operating system. If you forget to declare something your app simply will not be able to do that operation. Beware that starting from Android 10 the access to the external |
^ READ_EXTERNAL_STORAGE | ^ READ_EXTERNAL_STORAGE | ||
Line 209: | Line 209: | ||
The **compile SDK** is the environment you want to use to create the app, i.e. the SDK you downloaded from Google (which generally support the higher API available at the moment). This will affects what functions and constructs you can use in your program. If you do not specify a version, Buildozer should detect the highest SDK downloaded and use it. In our case only one SDK was downloaded, and it was SDK API 31. | The **compile SDK** is the environment you want to use to create the app, i.e. the SDK you downloaded from Google (which generally support the higher API available at the moment). This will affects what functions and constructs you can use in your program. If you do not specify a version, Buildozer should detect the highest SDK downloaded and use it. In our case only one SDK was downloaded, and it was SDK API 31. | ||
- | ==== Compiling the package ==== | + | ==== Compiling the package |
- | 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). | + | 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). |
< | < | ||
buildozer android debug | buildozer android debug | ||
</ | </ | ||
+ | |||
+ | The package will be created into the **bin/** subdirectory, | ||
+ | |||
+ | When you are ready to **publish** your package, you must create the //release// binary: | ||
< | < | ||
Line 221: | Line 225: | ||
</ | </ | ||
- | The package | + | In this case the package created into the **bin/** subdirectory |
===== Web Resources ===== | ===== Web Resources ===== |
doc/appunti/prog/kivy_debian_12_android_11.txt · Last modified: 2024/04/04 07:31 by niccolo