-
Notifications
You must be signed in to change notification settings - Fork 508
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
Problem on debug with android.features. #1715
Comments
Just confirming that:
We should either: (a) Add the ability to p4a, and have tests to show it works, or: |
Thanks for your attention, would you please helping me to add this feature to p4a?. |
Tnx, do you have any idea to fix this? |
Sorry, no. It is outside my expertise. I have no idea what "--feature" is even supposed to do. For all I know, p4a supports the concept, but doesn't call it "--feature". If it were left to me, I would simply remove the feature from Buildozer, and say "It isn't supported (yet) until p4a supports it." but that won't solve your problem, so I am keeping my hands off. I am hoping someone more familiar with the project over time will be able to give a little history of why it was added to Buildozer in the first place. |
Thanks body @Julian-O, by your Guides. I found that, create a file |
I understand you have a work-around, but I think this should be reopened, so the problem (Buildozer advertises an unsupported option that generates bad parameters for p4a) can be resolved. |
Versions
Description
I uncomment
android.features = android.hardware.usb.host,
and do buildozer android debug, and the output is[unrecognaize](toolchain.py: error: unrecognized arguments: --feature) android.hardware.usb.host
buildozer.spec
Command:
`buildozer android debug `
Spec file:
Logs
The text was updated successfully, but these errors were encountered: