Skip to content
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

Provide custom path for android SDK to buildozer #237

Closed
udiboy1209 opened this issue Oct 13, 2015 · 7 comments
Closed

Provide custom path for android SDK to buildozer #237

udiboy1209 opened this issue Oct 13, 2015 · 7 comments

Comments

@udiboy1209
Copy link
Contributor

I frequently use Android Studio for development, and have a regularly updated collection of SDKs of different android versions in a specific directory.

I don't want buildozer to keep its own set of SDKs separately under ~/.buildozer/

Is there any global configuration I can edit to specify this to buildozer?

Currently using the latest stable version from pip : 0.30

@pythonic64
Copy link
Contributor

There is in buildozer.spec file:
https://github.com/kivy/buildozer/blob/master/buildozer/default.spec#L84

Set path to android sdk directory and remove "#"

@dessant
Copy link
Contributor

dessant commented Oct 13, 2015

@pythonic64 thanks for the quick solution. 👍

@dessant dessant closed this as completed Oct 13, 2015
@udiboy1209
Copy link
Contributor Author

Is there a global buildozer.spec so I dont have to do it for every project? I guess I could update default.spec in the source, but that would not allow me to change the location later. I'd have to change the spec file for every project I build.

P.S. from what I understand about default.spec, it is used to generate a buildozer.spec when buildozer init is run. But I may be wrong here!

@akshayaurora
Copy link
Member

@udiboy1209 use symlinks; symlink your android ndk and sdks folder to where bulldozer expects them to be in ~/.buildozer/...

@inclement
Copy link
Member

You can set it globally with the APP_ANDROID_SDK_PATH and APP_ANDROID_NDK_PATH environment variables. It's actually possible to set any buildozer.spec token this way - note that the initial APP refers to the section of the spec file, [app].

@udiboy1209
Copy link
Contributor Author

@akshayaurora and @inclement thanks for the nice hack! Although I would like to implement a global config file, probably situated in ~/.buildozer/global.spec. Just seems better.

I'll have to merge configs from both global.spec and the local buildozer.spec giving the latter more priority, right? I found the project uses ConfigParser. Am I in the right direction?

@udiboy1209
Copy link
Contributor Author

@inclement I just understood what you were trying to say after looking at set_config_token_fron_env().

So I guess a global file isn't needed then! Thanks everyone for your help 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants