| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
...containing, besides the original sources, all generated machine-independent
files needed for creating a bootstrap bazel without the need of having a protoc
installed.
--
Change-Id: Ib90e7896615b4067175a23fe2c942dbac4b71e4a
Reviewed-on: https://bazel-review.googlesource.com/#/c/6730
MOS_MIGRATED_REVID=136910561
|
|
|
|
|
|
|
| |
Currently, the proto only includes the linkopt arguments collected from the rules, which are insufficient for reconstructing the linking step in the extra action listener. This CL adds the complete command line needed to re-run the linking step.
--
MOS_MIGRATED_REVID=136211307
|
|
|
|
|
|
|
| |
new AIDL files in relation to their location.
--
MOS_MIGRATED_REVID=134687843
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=134651940
|
|
|
|
|
|
|
|
|
| |
signing scheme added behind a flag in commit 602f3ae70f49bd8bae6205a93f3df5918d3bacac.
RELNOTES:
--
MOS_MIGRATED_REVID=133877396
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, all classes from the symbol table are added to jdeps,
even if some of them haven't been resolved and as such aren't
actually used. This causes siblings from other jars (such as
R.java) to be added to jdeps, even though they are not actually
referenced. Mark these with Kind.UNRESOLVED to allow code to
discard these.
All non-test code that references Kind.IMPLICIT has been
modified to also check for Kind.INCOMPLETE to keep
the current behavior unchanged.
Eg:
jar liba.jar:
package a;
class A {
void test() {
// Use R.id
}
}
jar liba_resources.jar:
package a;
class R {
}
package b;
import a;
class MyClass {
A a = new A();
}
---> jdeps will contain both liba.jar, liba_resources.jar
the latter will now have Kind.INCOMPLETE.
--
MOS_MIGRATED_REVID=133791687
|
|
|
|
|
|
|
| |
RELNOTES: Remove deprecated absolute paths in blaze IDE artifacts
--
MOS_MIGRATED_REVID=133758389
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133584935
|
|
|
|
|
|
|
| |
ContentDigests function.
--
MOS_MIGRATED_REVID=133256094
|
|
|
|
|
|
|
|
|
|
| |
https://docs.google.com/document/d/1hh63AzKlwcOJN6jBZzY3GNPffzww-JKx1015DfFKM6g/edit#
The current version is kept intact for now, will remove it in the CL that does
the appropriate refactoring.
--
MOS_MIGRATED_REVID=132572182
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Any java rule that mixes generated and non-generated sources
will produce a filtered jar containing only the generated
output.
For a java rule with only "normal" sources or only generated
source files, no filtered jar is produced.
This will allow the IDE to resolve those generated sources.
RELNOTES:None
--
MOS_MIGRATED_REVID=132113568
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=130938527
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=130016248
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
I want to do this in a way that exposes the data attribute only for android_test and android_binary, so I'll add it to the deploy manifest instead.
*** Original change description ***
Expose test "data" attribute to IDE.
This is needed to deploy android_tests to the device for testing. For
symmetry we expose it for all tests rules.
--
MOS_MIGRATED_REVID=129926351
|
|
|
|
|
|
|
|
| |
This is needed to deploy android_tests to the device for testing. For
symmetry we expose it for all tests rules.
--
MOS_MIGRATED_REVID=129918247
|
|
|
|
|
|
|
| |
infrastructure to allow other artifact categories (such as debug symbols or compiler outputs) to be defined in other changes.
--
MOS_MIGRATED_REVID=128495797
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=128209793
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125385321
|