You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using kivy == master (with newtoolchain) in buildozer.spec, version 1.9.1 is downloaded. I've read somewhere that this option should download and compile the current master branch on github which is currently 1.9.2-dev0. In the kivy recipes of python-for-android, the init.py file has a hard reference to 1.9.1.
Is it normal behavior ?
Anybody has a solution for packaging latest master ?
The text was updated successfully, but these errors were encountered:
The recipe should fetch the version according to the value in buildozer, at least that was the way how old recipes worked. Try to print the url if the version was changed to .../archive/master... or not.
Also, the latest master doesn't work right now, because of some changes of compilation (see kivy/kivy#4832 ), therefore if you really need master, your best guess is to use latest commit without those changes. It should work even with replacing version with the hash.
When you do kivy==master, it won't redownload or check if master changed between your latest download of kivy and the spec. Just clean the cache, and it will redownload according to your requirements
When using
kivy == master
(with newtoolchain) in buildozer.spec, version 1.9.1 is downloaded. I've read somewhere that this option should download and compile the current master branch on github which is currently 1.9.2-dev0. In the kivy recipes of python-for-android, the init.py file has a hard reference to 1.9.1.Is it normal behavior ?
Anybody has a solution for packaging latest master ?
The text was updated successfully, but these errors were encountered: