Skip to content
This repository has been archived by the owner on Sep 6, 2020. It is now read-only.

Use ANDROID_HOME environment variable to locate SDK #11

Closed
wants to merge 1 commit into from

Conversation

vkotovv
Copy link

@vkotovv vkotovv commented Mar 6, 2013

Just updated build.xml via command android update project --path android-websockets to get an option to locate SDK with env variable. Was introduced in one of the recent versions of SDK tools.
This could be helpful for using Jenkins to build project depending on the android-websockets library.

build.xml was updated to the latest SDK version (21.1).
@koush
Copy link
Owner

koush commented Mar 6, 2013

use local.properties to set up sdk.dir. That's how this is supposed to be done.

# This file is automatically generated by Android Tools.
# Do not modify this file -- YOUR CHANGES WILL BE ERASED!
#
# This file must *NOT* be checked into Version Control Systems,
# as it contains information specific to your local configuration.

# location of the SDK. This is only used by Ant
# For customization when using a Version Control System, please read the
# header note.
sdk.dir=/Users/koush/src/android-sdk

@koush koush closed this Mar 6, 2013
@vkotovv
Copy link
Author

vkotovv commented Mar 6, 2013

Yes, that's true that one option is to use local.properties. This is one way of how it's supposed to be done. However, this piece of code was added to the SDK tools to provide alternative method. What I'm trying to say that build.xml was generated a year ago and now is outdated. If you use android update project command for the fresh project, this snippet will be there, you can try. So my idea was to update build.xml to the latest version. Please refer to similar request.
Regarding Jenkins build, it is easier to set $ANDROID_HOME variable once rather than adding local.properties for every Jenkins job.

@koush
Copy link
Owner

koush commented Mar 6, 2013

Oh gotcha. I've refreshed the build.xml w/ the android sdk locally and pushed. Thanks for the notice.

@koush
Copy link
Owner

koush commented Mar 6, 2013

a6a3b99

@vkotovv
Copy link
Author

vkotovv commented Mar 7, 2013

No problem, thanks for updating this.

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

Successfully merging this pull request may close these issues.

2 participants