| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
message.
RELNOTES: None.
PiperOrigin-RevId: 153372617
|
|
|
|
|
|
|
|
| |
This prevents having to parse the category, and allows the category to potentially be used in the future for information about all options, included undocumented, hidden, or internal options.
Also rename DocumentationLevel to OptionUsageRestrictions, since INTERNAL was not really documentation related.
PiperOrigin-RevId: 153367769
|
|
|
|
|
|
|
|
|
| |
repositories.
Fixes https://github.com/bazelbuild/bazel/issues/2830
RELNOTES: None
PiperOrigin-RevId: 153367521
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
broken tests
*** Original change description ***
Init absent action configs for CppCompile actions
So far only link actions were initialized in CppLinkActionConfigs. This cl
changes this class to also initialize CppCompile actions. This is needed for
our ongoing work removing hard-coded flags from Bazel and moving them into
Crosstool.
RELNOTES: None.
PiperOrigin-RevId: 153366563
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
breaks tests
*** Original change description ***
Extract --sysroot flag from bazel and move it into crosstool
This is an encore of https://github.com/bazelbuild/bazel/commit/6127358c1799d8d83cebbd499edac89f869df41b .
RELNOTES: None.
PiperOrigin-RevId: 153351147
|
|
|
|
| |
PiperOrigin-RevId: 153349925
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks internal tests that use nonstandard crosstools
*** Original change description ***
Make C++ archiving use action_configs instead of hardcoded flags
RELNOTES: Use action_config in crosstool for static library archiving, remove ar_flag.
PiperOrigin-RevId: 153344597
|
|
|
|
|
|
|
|
| |
There's no reason an expansion flag should not expand to multiple values for a repeatable flag (a flag with allowMultiple set to true.) If this expansion flag is set in a SetValue policy, group its repeatable subflags into a single SetValue per subflag.
For an overridable SetValue policy on an expansion, any repeatable flag that it expands to should append its value, and not override the user's original values.
PiperOrigin-RevId: 153233784
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 153223511
|
|
|
|
|
|
|
|
|
| |
Canonicalize-flags will provide the expanded and filtered version of the policy passed to it as a command argument if also passed the command arg --canonicalize_policy. This is the version that would be actually applied to the command line in another command.
In this mode, it will not also print out the interpretation of the flags passed after "--", so to get both outputs, it will have to be run twice. This was to keep the output clean and easy to parse.
RELNOTES: new option for bazel canonicalize-flags, --canonicalize_policy
PiperOrigin-RevId: 153215518
|
|
|
|
| |
PiperOrigin-RevId: 153202296
|
|
|
|
|
|
|
| |
to avoid exceeding the command line length limit for libraries
with very large numbers of resources.
PiperOrigin-RevId: 153191465
|
|
|
|
|
|
| |
objc_proto_library without the portable_proto_filters attribute.
PiperOrigin-RevId: 153189663
|
|
|
|
|
|
|
|
|
| |
latter swallows all filesystem failures, and does not disambiguate missing files from filesystem problems.
The syscall cache now tracks IOExceptions if they are present, just as it does with readdir().
RELNOTES: None
PiperOrigin-RevId: 153185433
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
android_binary targets have their own R.java files (built from merging
dependencies and any resources that belong directly to the target). As such,
they don't need inherited R.java files at runtime. Taking these out makes for
smaller APKs and less inheritance from the target's dependencies.
Add a flag to control this behavior. Have it default to continue to include
R.class files as runtime dependencies so we can control rollout of this
behavior.
Add tests of android_binary to ensure the JAR is filtered out as appropriate,
and of android_robolectrictest to ensure that those tests still have access to
the JARs.
RELNOTES: none
PiperOrigin-RevId: 153177074
|
|
|
|
|
|
| |
`DefaultInfo in target` should always return `true` for any target.
PiperOrigin-RevId: 153166669
|
|
|
|
| |
PiperOrigin-RevId: 153161442
|
|
|
|
| |
PiperOrigin-RevId: 153140874
|
|
|
|
| |
PiperOrigin-RevId: 153096906
|
|
|
|
|
|
|
|
|
| |
In this way, all indices are reported with 1 being the smallest
possible. Also, the numbers fit better with the file names generated
for log files etc.
Change-Id: I7671e5a79dd47c3e3afac16108acaeacdf018fc5
PiperOrigin-RevId: 153080339
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 153058374
|
|
|
|
|
| |
RELNOTES: Use action_config in crosstool for static library archiving, remove ar_flag.
PiperOrigin-RevId: 153046587
|
|
|
|
|
|
|
|
|
| |
For transports that are purely local (like the ones writing to a local file),
it sometimes can be useful to skip path conversion and use the local paths directly.
Support this for the text and binary format file transports.
Change-Id: I2ac2e187ebb11ff82c4e1ddf4881ea54f9d4205d
PiperOrigin-RevId: 153044267
|
|
|
|
|
|
| |
any extra defines.
PiperOrigin-RevId: 153039146
|
|
|
|
|
|
| |
used.
PiperOrigin-RevId: 153020672
|
|
|
|
|
|
|
|
|
|
|
|
| |
This filegroup is used by the Android testing infrastructure to launch QEMU2
emulators.
This filegroup will only build correctly on Linux.
Tracking issue: https://github.com/bazelbuild/bazel/issues/903
RELNOTES: None
PiperOrigin-RevId: 153003267
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fa97703c1edf ("allow skylark implicit output callbacks to use the rule
name") fixed a limitation of the skylark implicit outputs by adding a
special case for "name" to the implicit outputs code. Later,
015e5954157a ("Remove special handling of name attribute") fixed the
general problem of "name" being a special case in the attribute
map. Therefore, we can remove my original fix. We may also excise an
older special case in the implicit outputs templating code.
Change-Id: I606c9decd98a8df492d2359abe540d3263f99fe1
PiperOrigin-RevId: 152974774
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 152965874
|
|
|
|
|
|
|
| |
The memory regression was introduced in https://github.com/bazelbuild/bazel/commit/360fb4d9a1e2c44154b17aeb866e07bac2dd1b5b , now default providers
are optimized and are built only on demand for all types of targets.
PiperOrigin-RevId: 152957220
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before this change, attributes with select() were completely skipped.
This doesn't attempt to merge "trivial" selects, e.g. even though:
attr = [":foo"] + select({"//conditions:default": [":bar"]})
always resolves to:
attr = [":foo", ":bar"]
this change still produces:
attr = [":foo"] + [":bar"]
We could merge these in a future change, if desired. But it's not
even clear that's desired. There's conceptual value in keeping the
lists separate since that's how they were originally written. That
gives users a cue to maybe refactor their rules.
RELNOTES[NEW]: "query --output=build" now includes select()s
PiperOrigin-RevId: 152956939
|
|
|
|
|
|
|
|
|
| |
Before this change Bazel was adding this implicitly. But that wasn't
working properly with --incremental_dexing. And that implementation is a
lot messier and bug-prone vs. just including it as a standard dependency.
Issue: #2694
PiperOrigin-RevId: 152956638
|
|
|
|
|
|
|
|
| |
This logger makes it easier to parse log statements and is now enabled for Bazel's java.log.
RELNOTES[INC]: Bazel now prints logs in single lines to java.log
PiperOrigin-RevId: 152954337
|
|
|
|
|
|
|
| |
This issues a configuration transition on the dependencies of the rule, causing deps to be compiled with the appropriate minimum os version.
RELNOTES: None.
PiperOrigin-RevId: 152952168
|
|
|
|
|
|
|
|
|
|
|
| |
This is the first actual user of the config_feature_flag rule, able to actually
set its value (and thus give a point to using it!)
This feature is not fully launched yet, but it is usable in any build
containing this change.
RELNOTES: None.
PiperOrigin-RevId: 152948153
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 152947523
|
|
|
|
|
|
| |
from an apple_binary split transition context. Refactors ProtobufSupport to not rely on ruleContext for dependencies.
PiperOrigin-RevId: 152939984
|
|
|
|
|
| |
Change-Id: I55fd5b2f38cad9d2b18d369ae51dbd93c2c92288
PiperOrigin-RevId: 152925304
|
|
|
|
| |
PiperOrigin-RevId: 152916191
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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: 152882585
|
|
|
|
|
|
|
|
| |
tool during incremental dexing
RELNOTES: none
PiperOrigin-RevId: 152838197
|
|
|
|
|
|
|
| |
This follows our CamelCaseInfo naming conventions for providers.
RELNOTES: None.
PiperOrigin-RevId: 152832215
|
|
|
|
| |
PiperOrigin-RevId: 152810023
|
|
|
|
|
|
|
|
| |
accidentally regressed.
TESTED=local RemoteWorker without work_path
RELNOTES: n/a
PiperOrigin-RevId: 152806430
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 152804937
|
|
|
|
|
|
|
| |
This is an encore of https://github.com/bazelbuild/bazel/commit/6127358c1799d8d83cebbd499edac89f869df41b .
RELNOTES: None.
PiperOrigin-RevId: 152803621
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 152800780
|
|
|
|
| |
PiperOrigin-RevId: 152799488
|
|
|
|
|
|
|
|
|
| |
Output artifacts are now always reported as named sets. So the
field for reporting artifacts directly in no longer needed. Clean
it up.
Change-Id: I41efc66116d4a733088d4ee685ccd3fcf0a62d05
PiperOrigin-RevId: 152799435
|