-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
android sdk tools: adapt path to file hierarchy changes #2681
base: develop
Are you sure you want to change the base?
Conversation
Recent Android SDK tools, including e.g. "8092744" and "8512546" [1][2], use a different path structure than e.g. "6514223" [0]. E.g. `sdkmanager` in older sdk tools used to be located at ${ANDROID_SDK_HOME}/tools/bin/sdkmanager but now it is at ${ANDROID_SDK_HOME}/cmdline-tools/bin/sdkmanager [0]: https://dl.google.com/android/repository/commandlinetools-linux-6514223_latest.zip [1]: https://dl.google.com/android/repository/commandlinetools-linux-8092744_latest.zip [2]: https://dl.google.com/android/repository/commandlinetools-linux-8512546_latest.zip Related: kivy#2540 kivy#2593
I have tested and successfully built an apk using this PR along with the related buildozer PR (kivy/buildozer#1511), using android sdk cli tools Note that these paths were ~recently changed for similar reasons in #2593, to also search at |
Hi @SomberNight ! From: https://developer.android.com/studio/command-line#tools-sdk
And as @dbnicholson said in #2593 :
So, I've just tried to install multiple versions (
I guess we have to migrate our docs and/or automated installs instead of supporting a new (non-standard) folder structure. |
Hmm, so are we not supposed to just simply unzip the tools google hosts, but are now expected to move stuff around to have a specific layout? |
I spent a while looking at this trying to figure out how to only download the command line tools once, but this is the bootstrapping procedure I came up with.
There's a couple |
Yeah, downloading it twice is not something super nice, but that's definitely the cleaner approach (IMHO). |
Recent Android SDK tools, including e.g. "8092744" and "8512546", use a different path structure than e.g. "6514223".
E.g.
sdkmanager
in older sdk tools used to be located at${ANDROID_SDK_HOME}/tools/bin/sdkmanager
but now it is at
${ANDROID_SDK_HOME}/cmdline-tools/bin/sdkmanager
Related:
#2540
#2593