| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
parameter.
--
MOS_MIGRATED_REVID=113730588
|
|
|
|
|
|
|
| |
anymore.
--
MOS_MIGRATED_REVID=113512761
|
|
|
|
|
|
|
| |
--
Change-Id: Ic5b08394e042fee48bf079620ecb18426455d838
Reviewed-on: https://bazel-review.googlesource.com/2230
MOS_MIGRATED_REVID=106480667
|
|
|
|
|
|
|
|
|
| |
Constants.ANDROID_DEP_PREFIX.
This regrettably entails adding the options parser to the embedded tools in the Bazel binary, but that's only a temporary measure until the embedded binaries are compiled (and not provided in source from)
--
MOS_MIGRATED_REVID=106379028
|
|
|
|
|
|
|
| |
validating includes and updating action inputs is clearly separated and easier to understand now.
--
MOS_MIGRATED_REVID=106298050
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
release. Note the following peculiarities of the current situation:
- Sandboxed execution still silently falls back to non-sandboxed execution due to LocalGccStrategy explicitly requesting local execution.
- However, builds are still correct due to local execution using hdrs_check.
- hdrs_check, even though it was intended to default to "strict" in Bazel from the start, is still set to "loose" by default, so you might accidentally be using non-declared header files in your cc_* targets. In this case, your builds will break when the default becomes hdrs_check=strict and sandboxing becomes available. It is recommended that you check whether your builds are affected, by specifying --hdrs_check=strict manually and fixing your BUILD files to explicitly list all used includes in the srcs / hdrs attributes of your cc_* targets.
These remaining issues will be fixed in an upcoming change.
This change also adds regression tests for the issue.
--
MOS_MIGRATED_REVID=105747212
|
|
|
|
|
|
|
| |
This requires changing all "//tools/language:target" implicit dependencies to "@tools//tools/language:target".
--
MOS_MIGRATED_REVID=105193805
|
|
|
|
|
|
|
|
|
|
|
| |
tools repository.
This is a no-op refactoring CL. The actual switch will be made once everything passes with the new setup.
As a side cleanup, change the awkward realAndroidSdk() / realAndroidCrosstoolTop() mechanism to a converter.
--
MOS_MIGRATED_REVID=104649067
|
|
|
|
|
|
|
|
|
|
|
| |
The headers were modified with
`find . -type f -exec 'sed' '-Ei' 's|Copyright 201([45]) Google|Copyright 201\1 The Bazel Authors|' '{}' ';'`
And manual edit for not Google owned copyright. Because of the nature of ijar, I did not modified the header of file owned by Alan Donovan.
The list of authors were extracted from the git log. It is missing older Google contributors that can be added on-demand.
--
MOS_MIGRATED_REVID=103938715
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102345574
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102341264
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102020499
|
|
|
|
|
|
|
|
|
|
|
| |
All the code paths to the baseline coverage action now go through the
InstrumentedFilesCollector, which only passes the local sources for baseline
coverage, which are only those files matching the instrumentation spec, which
in turn are only files that are valid for offline coverage (in combination
with the withBaselineCoverage flag).
--
MOS_MIGRATED_REVID=101935566
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101769828
|
|
|
|
|
|
|
| |
Instead, inject the list from the corresponding module.
--
MOS_MIGRATED_REVID=101769355
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101768878
|
|
|
|
|
|
|
| |
but due to the flag default value being true, some code behaved as if it was).
--
MOS_MIGRATED_REVID=99913146
|
|
|
|
|
|
|
|
|
| |
Also tweak the Android NDK CROSSTOOL file a bit so that it actually works.
Fixes #335.
--
MOS_MIGRATED_REVID=99377509
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in the WORKSPACE file.
The error reporting if an android_ndk_repository rule is present is not very user-friendly (it just uses the non-Android toolchain, resulting in compile errors) but given that --android_crosstool_top is an interim solution until we get reasonable multi-platform support, I suppose it's fine.
As a side effect, instead of prefixing fat APK output directories with "fat-apk-", we prefix Android output directories with "android-".
This makes it possible to build Android apps with zero command line options. Rejoice!
--
MOS_MIGRATED_REVID=98624120
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=97224936
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Note that despite the rule being present, Android support is still not functional: two tools (//tools/android:{aar_generator,resources_processor} are still missing (and are a-coming!)
--
MOS_MIGRATED_REVID=96099045
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to //tools/android: .
This is useful because we can then eventually implement an android_tools_repository() rule that lets Bazel download the Android tools from somewhere instead of requiring it to be in every workspace with Android tools.
The number of tools here is somewhat scary, therefore, I'm considering creating an android_tools rule which would have an attribute for each of these things.
Some non-trivial things about this CL:
- The labels to load are removed from AndroidConfiguration because they would resolve to e.g. //external:dx_jar, which labels just don't exist and I don't want to add dummy //external:labels not prefixed with android_
- RedirectChaser is taught how to chase redirect through bind() rules because the Android SDK is now found by //external:android_sdk -> //tools/android:sdk -> @androidsdk//:sdk . Ideally, it would be ///external:android_sdk -> @androidsdk//:sdk, but I figured I'd not fix that in this CL.
--
MOS_MIGRATED_REVID=96080553
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92474815
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
features.
Features on the rule level modify features that are enabled at the package
level. Note that this behavior is different from how the current command line /
package level interaction is, but we probably want to change the command line
behavior.
Alternative implementations considered:
a) using package-level features as default value for the rule attribute; this
would make it hard for future transitions; adding a completely new feature
to a package should not require updating all rules that have overrides
b) putting all positive features and all negative features from command-line,
package, and rule attribute into a positive and negative set, and subtract
the negative from the positive set; this is how the command-line features
worked previously, but it makes it impossible to enable a features that
is disabled at the package level just for one rule.
RELNOTES: Add 'features' attribute on the rule level.
--
MOS_MIGRATED_REVID=92448449
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90649566
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=88927024
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=88813915
|
|
|
|
|
|
|
| |
Constants.
--
MOS_MIGRATED_REVID=87823207
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=87809723
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=87806484
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=87621601
|
|
--
MOE_MIGRATED_REVID=85702957
|