| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will make it easier to build the desugarer tool from the Bazel source tree as an executable (deploy) jar and then use it for something else.
For example, with this CL, you can do the following steps to get a standalone
desugarer binary:
1. git clone https://github.com/bazelbuild/bazel
2. bazel build //src/tools/android/java/com/google/devtools/build/android/desugar:desugar_bin_deploy.jar
3. cp bazel-bin/src/tools/android/java/com/google/devtools/build/android/desugar/desugar_bin_deploy.jar ~/bin/desugar.jar
And then you can invoke desugar without bazel with `java -jar ~/bin/desugar.jar`.
https://github.com/bazelbuild/bazel/issues/2975
RELNOTES: None
PiperOrigin-RevId: 155629711
|
|
|
|
| |
PiperOrigin-RevId: 155287620
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add compile_jars Skylark accessor to JavaProvider. This outputs the
non-recursive set of jars needed to build with this target. Allows
Skylark tools to get the same set of compile_jars that JavaLibrary is
getting.
Added test that verifies Skylark was getting lists from both
compile_jars and transitive_runtime_jars of the expected length. Then,
verified (via test code) those nested sets were identical to the ones
provided by the java_library.
To reviewers:
First, would like to add documentation flags to these fields in
JavaProvider. Is it possible, instead of adding them to this map to
follow use the @SkylarkCallable annotation to expose methods on
JavaProvider instead? It would then also be nice to mark these as
experimental since won't really know the final API until
java_skylark_library sandwich is done.
I also tested this locally via bazel build //src:bazel and then doing
~/bazelsandbox/bazel/bazel-bin/src/bazel test SomeTarget in a different
repo that had a .bzl file trying to use compile_jars.
Change-Id: I1779c1b6303f36e50076c3479bfcb15a25aa95d8
PiperOrigin-RevId: 155191816
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/509.
Example output:
```
$ bazel build //:all
INFO: Found 1 target...
ERROR: /usr/local/google/home/ajmichael/.cache/bazel/_bazel_ajmichael/7fcc7480abc634522e5c0cfe6b85b583/external/bazel_tools/tools/android/BUILD:236:1: Executing genrule @bazel_tools//tools/android:no_android_sdk_repository_error failed: Process exited with status 1 [sandboxed].
This build requires an Android SDK. Please add the android_sdk_repository rule to your WORKSPACE.
Use --strategy=Genrule=standalone to disable sandboxing for the failing actions.
Target //:lib failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 0.327s, Critical Path: 0.10s
```
RELNOTES: Attempting to build an Android target without setting up android_sdk_repository will now produce a helpful error message.
PiperOrigin-RevId: 155158667
|
|
|
|
|
|
|
| |
Also, open source two more tests.
RELNOTES: None
PiperOrigin-RevId: 155129416
|
|
|
|
|
|
|
|
|
|
|
|
| |
The logic is already in Bazel but wasn't available to build rules.
This change makes it available, but still requires data binding's
{build|run}time libraries to be checked into appropriate depot
spots for everything to work.
Followup changes will make those libraries easily available.
Issue: #2694
PiperOrigin-RevId: 153359861
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
files for all android system images installed in the SDK. For system images that are not installed, create genrule "poison pills" that print a helpful error message if you attempt to build them.
These filegroups are intended to be used as the system_image attribute of the android_device rule.
Example:
$ bazel build @android_test_support//tools/android/emulated_devices/pixel:android_25_x86
Extracting Bazel installation...
.
INFO: Found 1 target...
ERROR: /usr/local/google/home/ajmichael/.cache/bazel/_bazel_ajmichael/efa32264346ef1fc4fec492202b88b31/external/androidsdk/BUILD.bazel:56:1: Executing genrule @androidsdk//:emulator_images_android_25_x86 failed: Process exited with status 1 [sandboxed].
This rule requires that the Android SDK used by Bazel has the following system image installed: emulator_images_android_25_x86. Please install this system image through the Android SDK Manager and try again.
RELNOTES: None
PiperOrigin-RevId: 152889824
|
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 152292294
|
|
|
|
|
|
|
|
| |
#1391
RELNOTES: None
PiperOrigin-RevId: 152179305
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 150372383
MOS_MIGRATED_REVID=150372383
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
this flag isn't needed with unknown commit
*** Original change description ***
Add --activity_name_file flag and modify --start flag in incremental_install. This is a first step
to add the ability for mobile-install to wait for the debugger before starting the app.
--
PiperOrigin-RevId: 150340712
MOS_MIGRATED_REVID=150340712
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 150194430
MOS_MIGRATED_REVID=150194430
|
|
|
|
|
|
|
|
| |
A previous change added this filegroup with the name %s_files. Recent discussions have suggested changing the naming convention to be a prefix instead before it is too late.
--
PiperOrigin-RevId: 150117207
MOS_MIGRATED_REVID=150117207
|
|
|
|
|
|
|
|
|
|
| |
incremental_install. This is a first step
to add the ability for mobile-install to wait for the debugger before starting the app.
--
PiperOrigin-RevId: 149897848
MOS_MIGRATED_REVID=149897848
|
|
|
|
|
|
|
|
|
|
| |
Also, remove some tests from android_integration_test.sh that are now covered by AndroidSdkRepositoryTest. This should hopefully reduce breakages of android_integration_test.sh that are not caught until the change makes its way to Jenkins.
I haven't yet figured out how to move the environment variable settings tests into AndroidSdkRepositoryTest.
--
PiperOrigin-RevId: 147864723
MOS_MIGRATED_REVID=147864723
|
|
|
|
|
|
|
|
| |
Creates filegroup containing sdk path in Bazel embedded Android SDK repository.
--
PiperOrigin-RevId: 147426838
MOS_MIGRATED_REVID=147426838
|
|
|
|
|
|
|
|
|
|
| |
This caused a failure in http://ci.bazel.io/job/Gerrit-bazel-tests/368/BAZEL_VERSION=latest,PLATFORM_NAME=ubuntu_15.10-x86_64/console
where the genrule used java from a jdk7 instead of a jdk8.
--
PiperOrigin-RevId: 147198518
MOS_MIGRATED_REVID=147198518
|
|
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/2222.
RELNOTES: Support for Java 8 lambdas, method references, type annotations and repeated annotations in Android builds with --experimental_desugar_for_android.
--
PiperOrigin-RevId: 147109786
MOS_MIGRATED_REVID=147109786
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rolling forward with fixes for the incremental tool.
*** Original change description ***
Automated [] rollback of commit d11d510c571b10787856395709f9ad945ca70bb2.
*** Reason for rollback ***
--
PiperOrigin-RevId: 146940409
MOS_MIGRATED_REVID=146940409
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
--
PiperOrigin-RevId: 146820790
MOS_MIGRATED_REVID=146820790
|
|
|
|
|
|
|
|
|
| |
This makes the code simpler as well as reducing the number of targets to build.
It also makes testing and profiling different action strategies vastly easier.
--
PiperOrigin-RevId: 146812659
MOS_MIGRATED_REVID=146812659
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 146300001
MOS_MIGRATED_REVID=146300001
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rollforward with fixes and a test. Previously AndroidSdkRepository required that system-images/ directory exist in the Android SDK. However, it does not exist until you download the first system image.
*** Original change description ***
Automated [] rollback of commit 06072c557290b97cb2d2e4fd255b647a9208cb5c.
*** Reason for rollback ***
Broke andriod_sdk_repository on ci.bazel.io
See https://github.com/bazelbuild/bazel/issues/2465
*** Original change description ***
Make android_sdk_repository discover all system-images directories in the sdk.
This will be used by the upcoming android_device rule that launches emulators.
--
PiperOrigin-RevId: 146258003
MOS_MIGRATED_REVID=146258003
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke andriod_sdk_repository on ci.bazel.io
See https://github.com/bazelbuild/bazel/issues/2465
*** Original change description ***
Make android_sdk_repository discover all system-images directories in the sdk.
This will be used by the upcoming android_device rule that launches emulators.
--
PiperOrigin-RevId: 146235800
MOS_MIGRATED_REVID=146235800
|
|
|
|
|
|
|
|
| |
This will be used by the upcoming android_device rule that launches emulators.
--
PiperOrigin-RevId: 146183077
MOS_MIGRATED_REVID=146183077
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 146142811
MOS_MIGRATED_REVID=146142811
|
|
|
|
|
|
|
|
| |
Note that these aliases are intentionally not yet functional. Nothing should be trying to build them.
--
PiperOrigin-RevId: 145746166
MOS_MIGRATED_REVID=145746166
|
|
|
|
|
|
|
|
| |
attributes if they aren't present in the original manifest. Before, it would make them None, and aapt would fail.
--
PiperOrigin-RevId: 145726642
MOS_MIGRATED_REVID=145726642
|
|
|
|
|
|
|
|
| |
Saves 12kB! :)
--
PiperOrigin-RevId: 144997917
MOS_MIGRATED_REVID=144997917
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
api_level is no longer required. It now sets the default android_sdk that is used if the --android_sdk flag is not passed. If it is not set, the highest api_level will be used as the default.
The new behavior is demonstrated by the following example:
$ ls $ANDROID_HOME/platforms
android-21 android-22 android-23
$ cat WORKSPACE
android_sdk_repository(
name = "foo",
)
$ bazel build //java/my/app # uses api level 23
$ bazel build --android_sdk=@foo//:sdk-22 //java/my/app # uses api level 22
$ cat > WORKSPACE <<EOF
android_sdk_repository(
name = "foo",
api_level = 21,
)
EOF
$ bazel build //java/my/app # uses api level 21
$ bazel build --android_sdk=@foo//:sdk-23 //java/my/app # uses api level 23
See https://github.com/bazelbuild/bazel/issues/2284 for the master plan for android_sdk_repository.
RELNOTES: android_sdk_repository no longer requires api_level. If one is not specified, the highest android platform installed will be used. Furthermore, android_sdk's are created for all android platforms installed and can be specified with the --android_sdk flag.
--
PiperOrigin-RevId: 144258881
MOS_MIGRATED_REVID=144258881
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 143825037
MOS_MIGRATED_REVID=143825037
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This should help clear up the confusion that caused https://github.com/bazelbuild/bazel/issues/2283.
Now all of the following work:
bazel build //tools/android/...
bazel test //tools/android/...
bazel build @bazel_tools//tools/android/...
--
PiperOrigin-RevId: 143666995
MOS_MIGRATED_REVID=143666995
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
breaks bazel:
https://github.com/bazelbuild/bazel/issues/2283
http://ci.bazel.io/job/bazel-tests/432/BAZEL_VERSION=HEAD,PLATFORM_NAME=linux-x86_64/console
*** Original change description ***
Remove broken and unused Android tools aliases.
--
PiperOrigin-RevId: 142768488
MOS_MIGRATED_REVID=142768488
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 142702623
MOS_MIGRATED_REVID=142702623
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rolling forward, intentionally breaking loading phase (and therefore `bazel fetch`) for android_binary in Bazel if no android_sdk_repository is set up.
Will not submit until Tensorflow's use case is cleaned up in https://github.com/tensorflow/tensorflow/pull/6225.
--
PiperOrigin-RevId: 142068703
MOS_MIGRATED_REVID=142068703
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rollforward with fixes to android_integration_test.sh. The test now uses the new syntax for the Support Library AARs.
All CIs that have been created since last December should have this library installed due to https://github.com/bazelbuild/continuous-integration/blob/master/mac/mac-android.sh#L36.
*** Original change description ***
Automated [] rollback of commit f699b502ef6a57dc68570486191ad1c318e8fd1b.
*** Reason for rollback ***
Breaks android_integration_test.sh which relies on the old targets.
I don't have time to update the test to use the new targets at the moment, so rolling the change back for now.
https://github.com/bazelbuild/bazel/issues/2159
RELNOTES:
--
PiperOrigin-RevId: 141233182
MOS_MIGRATED_REVID=141233182
|
|
|
|
|
|
|
|
|
|
|
|
| |
A followup change will remove the apksigner jar that is bundled with Bazel.
RELNOTES: Bazel Android builds use the apksigner tool from the Android SDK
build-tools. Bazel Android builds now require build-tools version 24.0.3 or
later.
--
PiperOrigin-RevId: 141181612
MOS_MIGRATED_REVID=141181612
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks android_integration_test.sh which relies on the old targets.
I don't have time to update the test to use the new targets at the moment, so rolling the change back for now.
https://github.com/bazelbuild/bazel/issues/2159
RELNOTES:
--
MOS_MIGRATED_REVID=140733556
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In December 2015, these JARs needed for these targets were removed from all subsequent Android SDK releases. They were replaced by a two local maven repositories:
<android sdk>/extras/android/m2repository and <android sdk>/extras/google/m2repository. Furthermore, the new dependencies are AARs and the Maven repositories are sem-ver'd so the developer needs to select the version of the library to use.
In https://github.com/bazelbuild/bazel/commit/2fcf0e I added support for android_sdk_repository to parse these local maven repositories and generate java_import and aar_import rules along with their dependencies.
Since these "extras" do not ship with the SDK by default and are not versioned with the build-tools, you cannot currently download the old JAR versions. As such, anyone who has updated their Android SDK in the last year should not have been able to download the old JARs.
See https://github.com/bazelbuild/bazel/issues/1745 for the tracking issue and information on migrating from the old targets to the new ones.
RELNOTES: Top level @androidsdk support library targets have been replaced by @androidsdk//<group id>:<artifact id>-<version> for Android SDK Support and Google Play Services libraries.
--
MOS_MIGRATED_REVID=140562616
|
|
|
|
|
|
|
| |
RELNOTES:
--
MOS_MIGRATED_REVID=139370787
|
|
|
|
|
|
|
| |
Now, apks can be built faster in Bazel using the --use_singlejar_apkbuilder flag.
--
MOS_MIGRATED_REVID=139285943
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138516288
|
|
|
|
|
|
|
|
| |
Prior to this change, the android SDK for the integration tests was empty so
they were not run.
--
MOS_MIGRATED_REVID=137307968
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137209855
|
|
|
|
|
|
|
|
|
|
|
| |
In commit 78c19807d2cbb308b830022dcdcc8b03f19f90a9 I accidentally broke aar_import when I moved
zip_manifest_creator from tools/android to tools/zip because tools/android does
not have separate BUILD and BUILD.tools files. The test did not catch this,
because the dependency in tools/android/BUILD is correct in the context of the
bazel tree but not in the context of the bazel_tools embedded workspace.
--
MOS_MIGRATED_REVID=137209500
|
|
|
|
|
|
|
| |
See https://github.com/bazelbuild/bazel/issues/1935
--
MOS_MIGRATED_REVID=137202533
|
|
|
|
|
|
|
| |
The libs that are extracted are dependent on the CPU from the Android split transition. This is set either from --fat_apk_cpu or --android_cpu if fat_apk_cpu is empty.
--
MOS_MIGRATED_REVID=137188695
|
|
|
|
|
|
|
| |
Also moves AAR-specific tools from tools/zip into tools/android and renames embedded_jar_extractor to aar_embedded_jars_extractor because in a future change it will extract classes.jar and libs/*.jar.
--
MOS_MIGRATED_REVID=136099324
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/bazel/test-setup.sh uses this filegroup to symlink the contents
of the Android SDK into the workspace for the test. However, since we add BUILD
files into the Android SDK, we don't want to copy those into the workspace
because they will be regenerated by the integration test.
Fixes https://github.com/bazelbuild/bazel/issues/1927.
--
MOS_MIGRATED_REVID=135858750
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=135805730
|