| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
The user interface is not changing. The policy will still be accepted as a flag passed to the client, as a startup flag (before the command), it will just no longer trigger server restarts and will not be passed on to a bazel server as part of the startup arguments. In batch mode, however, it will still be a startup argument, because the RunRequest proto is not sent, and all invocations restart bazel in batch mode anyway.
Since invocation policy only affects command arguments, and changes in command arguments do not cause server restarts, this is consistent with other server restart behavior.
RELNOTES: Changing --invocation_policy will no longer force a server restart.
PiperOrigin-RevId: 152426207
|
|
|
|
| |
PiperOrigin-RevId: 152173189
|
|
|
|
|
|
|
|
|
| |
Closes https://github.com/bazelbuild/bazel/issues/1391.
RELNOTES: Removed --experimental_use_jack_for_dexing and libname.jack output of
android_library.
PiperOrigin-RevId: 152131075
|
|
|
|
| |
PiperOrigin-RevId: 151825956
|
|
|
|
|
|
|
| |
This isn't used anymore, it's the same as STRING_DICT, deleting so no one tries
to use it.
PiperOrigin-RevId: 151738915
|
|
|
|
|
|
|
|
| |
This change is one step towards removing --nouse_singlejar_apkbuilder.
RELNOTES: None
PiperOrigin-RevId: 151730390
|
|
|
|
|
|
|
|
|
| |
Record the starting times of test actions, so that they can be reported
in the build event protocol.
Change-Id: I28e8d7d6ad39d91f4ffdd8a6161a5fc30f9a39b8
PiperOrigin-RevId: 151724760
|
|
|
|
|
|
|
|
|
|
| |
Preparing for it to be a proper OnePlatform API.
TESTED=n/a
--
PiperOrigin-RevId: 150997585
MOS_MIGRATED_REVID=150997585
|
|
|
|
|
|
|
|
| |
Also warn that user values can be lost, at which point later policies won't revive them. This warning should be removed once [] is fixed.
--
PiperOrigin-RevId: 149939586
MOS_MIGRATED_REVID=149939586
|
|
|
|
|
|
|
|
|
|
|
|
| |
towards cross-platform support, we will add a hack that takes some values via
a command line flag, and pass them on to a remote execution engine (next CL).
TESTED=no change
RELNOTES: n/a
--
PiperOrigin-RevId: 149753326
MOS_MIGRATED_REVID=149753326
|
|
|
|
|
|
|
|
| |
via the target map.
--
PiperOrigin-RevId: 149666196
MOS_MIGRATED_REVID=149666196
|
|
|
|
|
|
|
|
|
| |
Add a field to the IntelliJ aspect proto which handles both current and future
formats.
--
PiperOrigin-RevId: 149559228
MOS_MIGRATED_REVID=149559228
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 2346f5a01561f695a2b2ba7655359d5020105077.
It breaks bazel build in freebsd[1]. The solution is to patch
https://svnweb.freebsd.org/ports/head/devel/protobuf/files/. I
rolled-back this since the other builds will not automatically start if
Bazel is broken.
[1] http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel/JAVA_VERSION=1.8,PLATFORM_NAME=freebsd-11/1312/
Change-Id: I7e939a4293d799ab6dd67f93d219d1efdf4cd901
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 148375330
MOS_MIGRATED_REVID=148375330
|
|
|
|
|
|
|
|
|
| |
This enables both native and Skylark rules to declare attributes which
have labels/Targets as keys, and have string values.
--
PiperOrigin-RevId: 148365033
MOS_MIGRATED_REVID=148365033
|
|
|
|
|
|
|
| |
with some backports from HEAD
(:java_toolchain, internal_gen_well_known_protos_java)
Change-Id: I54be8809f411ec8cb02203b478f699e1fccb5f62
|
|
|
|
|
|
|
|
| |
The latter are the names in the upstream protobuf repo.
--
PiperOrigin-RevId: 147163206
MOS_MIGRATED_REVID=147163206
|
|
|
|
|
|
|
|
| |
Then use it in the blaze plugin's main class run configuration producer.
--
PiperOrigin-RevId: 146980092
MOS_MIGRATED_REVID=146980092
|
|
|
|
|
|
|
|
|
| |
This enables us to configure default features for each toolchain without having
to hard-code anything in class such as CcCommon.
--
PiperOrigin-RevId: 146904287
MOS_MIGRATED_REVID=146904287
|
|
|
|
|
|
|
|
| |
shared libraries.
--
PiperOrigin-RevId: 146655595
MOS_MIGRATED_REVID=146655595
|
|
|
|
|
|
|
|
| |
This rule allows deploying more than just a single jar. It can also read structure from pkgfilegroup, allowing deployment of non-single-jar plugins.
--
PiperOrigin-RevId: 145828461
MOS_MIGRATED_REVID=145828461
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144983864
MOS_MIGRATED_REVID=144983864
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 144348933
MOS_MIGRATED_REVID=144348933
|
|
|
|
|
|
|
|
|
|
|
|
| |
in C++.
Protocol was already exposed for Python and Java, only make C++ a first class citizen.
--
Change-Id: Ib2aa45bdb534f0f9181483b0161f2aa7c857dfb4
Reviewed-on: https://cr.bazel.build/7814
PiperOrigin-RevId: 144300665
MOS_MIGRATED_REVID=144300665
|
|
|
|
|
|
|
|
|
|
| |
This feature allows us to expand a flag_group when a build variable is not
available. This is helpful when migrating crosstools in a backward compatible
way (that works with released bazel as well as with bazel at HEAD).
--
PiperOrigin-RevId: 143955333
MOS_MIGRATED_REVID=143955333
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 143482476
MOS_MIGRATED_REVID=143482476
|
|
|
|
|
|
|
|
|
| |
This will be used by LibrariesToLinkValue to switch on many different types of
libraries.
--
PiperOrigin-RevId: 143438434
MOS_MIGRATED_REVID=143438434
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If an Aspect registered an action that an extra-action is
shadowing, its name is used when creating the extra-action's ID and
name.
Since recently, an aspect can see other aspects applied to the same
target. This CL record the names of other aspects applied to the target
as well, disambiguating the action owners.
--
PiperOrigin-RevId: 142264153
MOS_MIGRATED_REVID=142264153
|
|
|
|
|
|
|
|
| |
Nothing too detailed, a basic outline.
--
PiperOrigin-RevId: 141205173
MOS_MIGRATED_REVID=141205173
|
|
|
|
|
|
|
|
|
|
| |
This cl adds support for expand_if_true and expand_if_false messages
to the flag_group, allowing more elegant design of build variables.
This cl also adds IntegerValue VariableValue subclass.
--
PiperOrigin-RevId: 140849578
MOS_MIGRATED_REVID=140849578
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=140769347
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=140742419
|
|
|
|
|
|
|
|
|
| |
android_studio_ide_info -> intellij_ide_info
RuleIdeInfo -> TargetIdeInfo
Drop "rule" from all sub-ide infos (eg. JavaRuleIdeInfo -> JavaIdeInfo)
--
MOS_MIGRATED_REVID=140438983
|
|
|
|
|
|
|
| |
preparation of removing the older one from //third_party/protobuf.
--
MOS_MIGRATED_REVID=140023015
|
|
|
|
|
|
|
|
|
|
| |
With the recent addition of structured variables to CROSSTOOL we now need a way
how to conditionally expand various flag_groups depending on the presence of
particular build variable or its fields. This cl adds this support to flag
groups.
--
MOS_MIGRATED_REVID=139466070
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This cl adds a 3rd type of build variable - structs. Structs have fields, which
can hold any build variable type (including structs). In the CROSSTOOl, the
fields are accessed by the dot-notation, e.g.:
flag_group {
iterate_over: "libraries_to_link
flag_group {
iterate_over: "libraries_to_link.libraries"
flag: "-L%{libraries_to_link.libraries.directory}"
}
}
As a memory optimization, we also add StructureSequences. These save us from
the overhead of individual StructureValue objects.
--
MOS_MIGRATED_REVID=138851774
|
|
|
|
|
|
|
| |
not quoted or escaped.
--
MOS_MIGRATED_REVID=138717385
|
|
|
|
|
|
|
| |
owners of actions.
--
MOS_MIGRATED_REVID=138522535
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now flag_group can be marked with iterate_over field, that denotes for which
sequence variable the flag_group will be expanded repeatedly. This cl does that
in backwards compatible way as before, the iteration happened implicitly when the
used variable was found to be sequence at runtime. Because of that it adds some
extra code that will be removed once all the crosstools are migrated to the
explicit iteration.
--
MOS_MIGRATED_REVID=138501033
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138182982
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137669164
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137178015
|
|
|
|
|
|
|
|
|
| |
a value to use instead of the given flag value if it is disallowed by the
policy. This is a generalization of the existing new_default_value behavior to
cover any value of the flag, not just the default value if the flag is unset.
--
MOS_MIGRATED_REVID=137104944
|
|
|
|
|
|
|
| |
option to setting remote execution cache.
--
MOS_MIGRATED_REVID=137027196
|