Allow setting paths to android NDK and SDK from bazelrc

[mrdomino]

It'd be great to be able to set the paths to the android SDK and NDK tools without having to edit the WORKSPACE file, to accommodate variations among dev environments. I guess build:android --android_sdk_path=... would make sense, for instance?

[damienmg]

Lukacs to expose his plan on this one.

[lberki]

My plan for this one was that you'd have references in your WORKSPACE file to different SDKs, i.e.

android_sdk_repository(name="lollipop", ...)
android_sdk_repository(name="kitkat", ...)

And then you'd be able to select between them using the --android_sdk_top command line option. You can actually do this with Bazel right now (modulo any bugs)

What variations in dev environments you want to accommodate? Variations for a single developer (i.e. sometimes I want to build for L, sometimes for M) or variations between different developers (i.e. Alice has her SDK installed at a different place than Bob)?

[mrdomino]

Variations between developers: I have my sdk at /Users/me/sdk, someone else
has it at /opt/local/android-sdk-macosx, someone else has it at
/home/them/sdk.

I suppose this is achievable today with an ignored symlink and instructions
to set it appropriately. Then the WORKSPACE points to the symlink and no
one has to worry about keeping local commits out of the repo.
On Mon, Jul 27, 2015 at 05:54 lberki notifications@github.com wrote:

My plan for this one was that you'd have references in your WORKSPACE file
to different SDKs, i.e.

android_sdk_repository(name="lollipop", ...)
android_sdk_repository(name="kitkat", ...)

And then you'd be able to select between them using the --android_sdk_top
command line option. You can actually do this with Bazel right now (modulo
any bugs)

What variations in dev environments you want to accommodate? Variations
for a single developer (i.e. sometimes I want to build for L, sometimes for
M) or variations between different developers (i.e. Alice has her SDK
installed at a different place than Bob)?

—
Reply to this email directly or view it on GitHub
#326 (comment).

[lberki]

My master plan for that was user-specific WORKSPACE files. Once "load()" works in WORKSPACE files (they probably do today), you can do a load("WORKSPACE.user") in the WORKSPACE file and add WORKSPACE.user to your .gitignore.

Would this work?

[mrdomino]

Yup, that'd be awesome.

[lberki]

Filed #337 .

Then I close this as Working as Intended, since it doesn't really mesh with our medium term plans.