| Commit message (Collapse) | Author | Age |
|
|
|
| |
PiperOrigin-RevId: 153403092
|
|
|
|
|
|
|
|
|
| |
These are two different concepts. Do not remove category overload compatibility in this CL, to keep this change limited to converting the current uses of category.
With some flyby formatting fixes on affected OptionsBases.
RELNOTES: None.
PiperOrigin-RevId: 153390002
|
|
|
|
|
|
|
| |
This lets us easily get all options classes of a parser, or all fields of those options classes, in a deterministic way.
RELNOTES: None
PiperOrigin-RevId: 153376699
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 153360877
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
OptionsParserTest is kind of massive. This CL splits off tests that only concern IsolatedOptionsData. For example, tests that deal with malformed option specifications, but not string parsing, would go here.
A followup CL will add tests of IsolatedOptionsData's accessor methods.
Also added a unit test for the warning added by https://github.com/bazelbuild/bazel/commit/e11775c2394fc48ac7fe5b632b47ae952dd552b4.
RELNOTES: None
PiperOrigin-RevId: 153346363
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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: n/a
PiperOrigin-RevId: 153230139
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Refactoring: Wrapped the SymbolLoader and SymbolWriter in a single class.
RELNOTES: None
PiperOrigin-RevId: 153194543
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel/commit/4a303e2cd840810b95cbc793e38bdca48e6d9556
Only unescape @@-quoted args once
PiperOrigin-RevId: 153189611
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
This reverts commit 5235d06159ba6fee412bee261ea7867d061252b0.
Unfortunately, we noticed several build errors / test failures internally due this
change.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update protobuf to @laszlocsomor's fork of protobuf. This is essentially
the development version of protobuf 3.2.0 and windows specific fixes
from laszlo. Those fixes will be merged into protobuf soon:
https://github.com/google/protobuf/pull/2969).
For instructions on how to update protobuf for bazel see
README.bazel.md.
Change-Id: Ic1daafe30270cb6bcc6231e6c94fb670af0475e7
|
|
|
|
| |
PiperOrigin-RevId: 153140874
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
kokoro failures were not flakes :(
*** Original change description ***
Fix escaping of '@' in javabuilder command lines
"@" is used to denote params files, so when it appears in labels it is
escaped as "@@". The second "@" should be removed during flag parsing
to avoid e.g. having it show up in strict deps errors.
See bazelbuild/buildtools#83
PiperOrigin-RevId: 153127997
|
|
|
|
|
|
|
|
|
|
| |
"@" is used to denote params files, so when it appears in labels it is
escaped as "@@". The second "@" should be removed during flag parsing
to avoid e.g. having it show up in strict deps errors.
See bazelbuild/buildtools#83
PiperOrigin-RevId: 153098855
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
It is no longer used since --use_singlejar_apkbuilder is the default.
A future change will remove apkbuildermain from the Bazel codebase.
4MB bazel binary size savings! :)
RELNOTES: None
PiperOrigin-RevId: 153079733
|
|
|
|
|
|
|
|
|
| |
xcode src directories
There's no value in having these copied over from src/tools to tools/objc separately.
RELNOTES: None.
PiperOrigin-RevId: 153060955
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 153058374
|
|
|
|
|
|
|
|
|
| |
Bazel binary installer contains empty files because of the line that wasn't removed while packaging bazel_tools inside bazel.
Fixes: https://github.com/bazelbuild/bazel/issues/2662
Change-Id: I53a1f74566c48c3458ced2d46362873a68b6bf49
PiperOrigin-RevId: 153048191
|
|
|
|
|
| |
RELNOTES: Use action_config in crosstool for static library archiving, remove ar_flag.
PiperOrigin-RevId: 153046587
|
|
|
|
| |
This reverts commit ea82aa115794b019472b44d4f94ed902c1217f30.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update protobuf to @laszlocsomor's fork of protobuf. This is essentially
the development version of protobuf 3.2.0 and windows specific fixes
from laszlo. Those fixes will be merged into protobuf soon:
https://github.com/google/protobuf/pull/2969).
For instructions on how to update protobuf for bazel see
README.bazel.md.
Change-Id: I4f663955b0baeea3232b69ce32d9292427f5274a
|
|
|
|
| |
Change-Id: I17be35088c18e041c965bfdc0ad043271e152d44
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
ci.bazel.io fails because this shell script is not executable.
PiperOrigin-RevId: 153042368
|
|
|
|
|
|
|
| |
Fixes #2805.
RELNOTES: None.
PiperOrigin-RevId: 153039178
|
|
|
|
|
|
| |
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
|
|
|
|
| |
PiperOrigin-RevId: 152979269
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|