Dynamic setting of extractPackages
#106
Merged
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.
This PR adds the ability to dynamically set packages to be extracted via
extractPackagesvia aextract-packages.txtfile. This adds the possibility in briefcase to define these packages inbriefcase buildand not inbriefcase create.To set breakpoints when debugging via VSCode (see beeware/briefcase#2351), the packages to be debugged must first be extracted so that debugpy can map the breakpoints set on the host PC to those on the Android device via the path mappings. For this mapping, however, the .py files must be located on the Android file system and therefore be extracted. However, since this extraction leads to a longer startup time, this should only be done for debug builds via
briefcase build --debug. Currently it is only possible to specifyextractPackagesduringbriefcase create. Butbriefcase createhas no--debugoption, and I dont think it is worth adding it to create.briefcase-repo: https://github.com/timrid/briefcase
briefcase-ref: feature/debugger-support-android
PR Checklist: