-
Notifications
You must be signed in to change notification settings - Fork 514
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add resources #1513
Add resources #1513
Conversation
For the logs: |
if ':' in resource: | ||
resource_src, resource_dest = resource.split(":") | ||
else: | ||
resource_src = resource | ||
resource_dest = "" | ||
cmd.append(realpath(expanduser(resource_src)) + ':' + resource_dest) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ouch, duplicating such logic on buildozer
may lead to something unexpected (E.g: I needed to recall how the no :
syntax worked on python-for-android
side.)
This is bad, but I'm NOT blaming you, since we're expanding paths on buildozer
side everywhere. ( Bad, and should be moved on python-for-android
? )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, absolutely, but as you point out this is consistent with for example https://github.com/kivy/buildozer/blob/master/buildozer/targets/android.py#L931L938
I choose to copy what is shown to work, it is the low risk implementation. And yes the whole interface needs a rewrite, and an automatic appclean, and the .spec reorganized into common and uncommon, and....
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a super-minor suggestion (typo) and a thought about something that you should not address ATM, but that we should care about if we want to avoid to break the user experience at some point in the future.
Co-authored-by: Mirko Galimberti <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thank you!
Complement to p4a PR