aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/main/java/com/google/devtools/build/lib/rules/android/AndroidBinary.java
Commit message (Collapse)AuthorAge
* Check that most output artifacts are under a directory determined by the ↵Gravatar Lukacs Berki2015-07-29
| | | | | | | | | repository and package of the rule being analyzed. Currently this directory is PACKAGE for rules in the main repository and external/REPOSITORY_NAME/PACKAGE for rules in other repositories. This is a plan to fix #293. Ideally, we would simply make it impossible to create artifacts not under that location, but in practice, we cannot do that because some rules do want to do this, mostly those that are already problematic due to shared actions. So the battle plan is to eliminate as many calls to AnalysisEnvironment.getDerivedArtifact() as I possibly can and audit the rest. -- MOS_MIGRATED_REVID=99351151
* Add a command line option to enable incremental installation for Android ↵Gravatar Lukacs Berki2015-07-27
| | | | | | | | | native libraries. This requires changes to the stub application and the installer script, which are a-coming. -- MOS_MIGRATED_REVID=99174902
* Adds gen jar and manifest proto outputs.Gravatar Alex Humesky2015-07-10
| | | | | | | Adds a jar output to Java and Android rules which contains the class files for source files generated from Java annotation processors. For a java_binary foo, the jar will be foo-gen.jar, and for a java_library foo the jar will be libfoo-gen.jar, and similarly for Android. Also adds a binary serialized proto manifest file output to Java and Android rules which describes the contents of the output class jar of those rules, which is used to create the -gen.jar. See src/main/protobuf/java_compilation.proto. -- MOS_MIGRATED_REVID=97793715
* Avoid crash when the Android stub application is not a Java rule.Gravatar Lukacs Berki2015-06-30
| | | | | -- MOS_MIGRATED_REVID=97227161
* Remove references to all Android tools from AndroidConfiguration.Gravatar Lukacs Berki2015-06-29
| | | | | | | | | Bazel unconditionally loads all the labels in configurations for now, and we don't want Android stuff to be loaded if the build doesn't have anything to do with Android. The alternative would be to fix this by not loading all configuration fragments, but this is the more expedient solution. The SDK will be dealt with by binding //external:android/sdk to a dummy SDK unless overridden by an android_sdk_repository rule. -- MOS_MIGRATED_REVID=97116824
* Remove support for non-android_sdk Android SDKs.Gravatar Lukacs Berki2015-06-24
| | | | | | | AndroidTools is not passed around anymore. This comes at the cost of having to remember to raise an error in every rule configured target factory, but I think this is preferable to shuttling a variable around. -- MOS_MIGRATED_REVID=96746874
* Add a tools/android/jack package to the Bazel tree so that Android rules ↵Gravatar Lukacs Berki2015-06-17
| | | | | | | | | actually work. This is a temporary measure until these targets are integrated into android_sdk . Also make handling invalid tools/android/jack packages in JackCompilationHelper a bit more robust. -- MOS_MIGRATED_REVID=96202009
* Adds a new input and output to resource processing, symbols txt, which will ↵Gravatar Googler2015-06-16
| | | | | | | be used to express the direct dependencies for resource processing. -- MOS_MIGRATED_REVID=96037997
* Remove the debug_key attribute from android_binary and the associated -ks ↵Gravatar Lukacs Berki2015-06-16
| | | | | | | argument from the ApkBuilder invocation, because it turns out that ApkBuilder doesn't support it. -- MOS_MIGRATED_REVID=96035676
* Various odds and ends in preparation for adding the Android rules to ↵Gravatar Lukacs Berki2015-06-12
| | | | | | | | | | | | BazelRuleClassProvider: - Add stub targets to tools/android/BUILD - Make Constants.ANDROID_DEFAULT_SDK non-constant so that the classfile can be replaced in the .jar - Make AndroidTools complain if --android_sdk does not point to an android_sdk rule. - Make the default visibility in the BUILD file generated by android_sdk_repository public -- MOS_MIGRATED_REVID=95816158
* Bugfix: actually link in the split stub application for "blaze ↵Gravatar Lukacs Berki2015-06-11
| | | | | | | mobile-install --split_apks". -- MOS_MIGRATED_REVID=95715203
* Enable AndroidBinary to dex with Jack.Gravatar Michael Staib2015-06-10
| | | | | | | | | | | | | Until the Jack aspect implementation is submitted (in a coming CL), only android_library dependencies can be used by Jack dexing, as no other rule type exports the right provider. But for now, android_binaries which depend purely on android_libraries can build their dexes using Jack if --experimental_android_dex_with_jack is specified. -- MOS_MIGRATED_REVID=95534421
* Changes zip filtering of the test APK to use the last jar before dexing from ↵Gravatar Googler2015-06-08
| | | | | | | the binary_under_test. This prevents the filter from removing classes that are identical in the deploy jars but are proguarded differently. -- MOS_MIGRATED_REVID=95325114
* Rollback of unknown previous commit.Gravatar Googler2015-06-05
| | | | | -- MOS_MIGRATED_REVID=95215123
* Use the -nf option of ApkBuilder (which is available in the Android SDK) ↵Gravatar Lukacs Berki2015-06-01
| | | | | | | | | instead of the -nl one (which is not) to include native libraries. The alternative implementation uses a symlink tree, but given that we never have many native libraries, I opted for the simpler approach. -- MOS_MIGRATED_REVID=94891099
* Use an aspect to calculate the Android neverlink libraries.Gravatar Lukacs Berki2015-05-29
| | | | | | | This cuts the .java -> .android dependency between Java packages, which is nice at the cost of some cavalier over-estimation of the direct dependencies in AndroidNeverlinkAspect. -- MOS_MIGRATED_REVID=94745544
* Move the source code of the Android rules to the Bazel tree.Gravatar Lukacs Berki2015-05-19
This is mostly a "[] mv", except for the extra constant that specifies the location of the Android SDK and moving the $zip attribute. They are minor enough to be included in this CL. Tested by creating a Bazel tree, compiling it and verifying that the Android classes are in libblaze.jar. I also eyeballed the source as a final check that nothing sensitive gets leaked. -- MOS_MIGRATED_REVID=93971892