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

mess with ANDROID_SDK_ROOT ANDROID_SDK_HOME ANDROID_HOME #34

Closed
Araminos opened this issue Jun 4, 2020 · 2 comments · Fixed by #39
Closed

mess with ANDROID_SDK_ROOT ANDROID_SDK_HOME ANDROID_HOME #34

Araminos opened this issue Jun 4, 2020 · 2 comments · Fixed by #39

Comments

@Araminos
Copy link
Contributor

Araminos commented Jun 4, 2020

"cargo apk run" checks ANDROID_HOME or ANDROID_SDK_HOME for sdk location, but according this clever answer :
ANDROID_SDK_HOME - Location of SDK related data/user files. Example: C:\Users<USERNAME>.android\ or ~/.android/. It is not a place for SDK
I am not able to find proof in official google site, but my experience say that is correct.

ANDROID_HOME - is deprecated. ANDROID_SDK_ROOT should be used instead. Google explains an algorithm of managing

  • If ANDROID_HOME is defined and contains a valid SDK installation, its value is used instead of the value in ANDROID_SDK_ROOT.
  • If ANDROID_HOME is not defined, the value in ANDROID_SDK_ROOT is used.
  • If ANDROID_HOME is defined but does not exist or does not contain a valid SDK installation, the value in ANDROID_SDK_ROOT is used instead.
@dvc94ch
Copy link
Contributor

dvc94ch commented Jun 4, 2020

Do you want to make a PR?

@Araminos
Copy link
Contributor Author

Araminos commented Jun 4, 2020

Do you want to make a PR?

Do you mean pull request or excuse me. I made something wrong? You are free to edit my posts as you wish. I I didn't know how to connect with you and tried to describe the problem most clearest way. I can delete it by myself.

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

Successfully merging a pull request may close this issue.

2 participants