Tried adding a recipe in .buildozer/android/platform/python-for-android/recipes but buildozer runs a git clean on the python-for-android install before every build which deletes it.
What is the intended method for adding custom recipes?
I'd really like to have this explained. The documentation kind of stops after explaining how to write your own recipe. It should tell us how to test that recipe, and how to deploy it for a particular application.
Yes, the documentation should be cleared about it. The idea is to contribute back to python-for-android, so you need to clone python-for-android, place your recipe in it, and use your own python-for-android version, not the default one.
Then you can do a Pull Request for including the new recipe into python-for-android.
So -- how do I test the recipe? How to deploy it? That is, if I clone python-for-android, and put my recipe in there, how do I tell buildozer to use that clone of python-for-android instead of the central location?
I see -- change the buildozer spec to point to it. Thanks!
Can you give an example of how to point the recipe to a different repository?
@jtoledo1974 p4a.local_recipes = ./src/python-for-android/recipes/ in buildozer.spec.
And in ./src/python-for-android/recipes/ is a path relative to your buildozer.spec and it contains your recipes.
For example in mine I currently have this:
$ find src/python-for-android/recipes/
src/python-for-android/recipes/
src/python-for-android/recipes/zbar
src/python-for-android/recipes/zbar/zbar-0.10-python-crash.patch
src/python-for-android/recipes/zbar/__init__.py
src/python-for-android/recipes/zbar/__init__.pyc
src/python-for-android/recipes/libiconv
src/python-for-android/recipes/libiconv/libiconv-1.15-no-gets.patch
src/python-for-android/recipes/libiconv/__init__.py
src/python-for-android/recipes/libiconv/__init__.pyc
src/python-for-android/recipes/libzbar
src/python-for-android/recipes/libzbar/__init__.py
src/python-for-android/recipes/libzbar/__init__.pyc
src/python-for-android/recipes/libzbar/werror.patch
Editing the local python for android repository and committing the changes also works just fine provided you don't run buildozer clean
Buildozer will use it with that commit
Most helpful comment
@jtoledo1974
p4a.local_recipes = ./src/python-for-android/recipes/inbuildozer.spec.And in
./src/python-for-android/recipes/is a path relative to yourbuildozer.specand it contains your recipes.For example in mine I currently have this: