Repository navigation
Building from a second checkout: refuse a dot-directory path; how to move a copied .buildozer cache - #20
Merged
Conversation
…move a copied .buildozer cache
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Syncs android-runner's new guard (PyDevices/android-runner#34) into this repo's
build_android.sh: buildozer leaves out every source file under a directory whose name starts with., so a checkout under one (a git worktree in.worktrees/) built an APK with no app in it. The script now stops at the start with the reason.docs/building.mdgets a short section on building from a second checkout: the dot-directory rule, and the one path indist_info.jsonto rewrite when you copyp4a_app/.buildozerfrom another checkout (otherwise packaging fails inmake_tar). Both came from PyDevices/android-runner#29.Checked by hand: run from
.worktrees/<name>, the script exits with status 2 and the message before it creates a venv.