| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 187356329
|
|
|
|
|
|
| |
This also gets rid of some static initialization cycles which we should try very hard to avoid in the future.
PiperOrigin-RevId: 187334087
|
|
|
|
| |
PiperOrigin-RevId: 187230977
|
|
|
|
| |
PiperOrigin-RevId: 187230702
|
|
|
|
| |
PiperOrigin-RevId: 187222454
|
|
|
|
| |
PiperOrigin-RevId: 187218309
|
|
|
|
| |
PiperOrigin-RevId: 187218260
|
|
|
|
| |
PiperOrigin-RevId: 187212799
|
|
|
|
|
|
| |
This flag changes the behavior of objc_library module map propagation so that module maps are only propagated to direct dependents, not transitive dependents. swift_library targets that import Objective-C code must then list those dependencies directly in its deps instead of depending on them being transitively present.
PiperOrigin-RevId: 187184692
|
|
|
|
|
|
|
| |
Progress on #4544.
RELNOTES: None.
PiperOrigin-RevId: 187179454
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
unknown commit fixes the only related broken target showing up in a TGP after
this change. It seems that this provider was only ever used through
java_wrap_cc with java_library dependencies which themselves had cc_library
dependencies, i.e. java_wrap_cc -> java_library -> cc_library. This dependency
is not needed, the cc_library can be added directly to java_wrap_cc to get the
same behavior and this is the way it should be done instead of relying on
transitive dependencies.
The reason for making this change right now is that with the Skylark C++ API, I
will be adding attr("deps").mandatoryProviders(CcCompilationInfo,
CcLinkParamsInfo) to C++ rules so that they can take any Skylark rule and not
having to explicitly hard-code the name of those Skylark rules in Blaze.
However, Java meets this criteria and the change would allow C++ rules to
depend on Java. This is not something that was supported before and is not
something we plan to support.
RELNOTES:none
PiperOrigin-RevId: 187158176
|
|
|
|
|
|
|
| |
will be used for the dependency checker later. Refactoring it now just avoids future potential merge conflicts.
RELNOTES: None
PiperOrigin-RevId: 187103807
|
|
|
|
| |
PiperOrigin-RevId: 187057628
|
|
|
|
| |
PiperOrigin-RevId: 187057332
|
|
|
|
| |
PiperOrigin-RevId: 187054284
|
|
|
|
|
|
| |
This field is needed by the Android Studio with Bazel plugin.
PiperOrigin-RevId: 187053906
|
|
|
|
| |
PiperOrigin-RevId: 187044297
|
|
|
|
| |
PiperOrigin-RevId: 187043046
|
|
|
|
| |
PiperOrigin-RevId: 187038647
|
|
|
|
| |
PiperOrigin-RevId: 187030267
|
|
|
|
|
|
|
|
|
|
|
| |
This cl introduces a bazel option
(--experimental_fix_linkstamp_inputs_bug_73447914) to control which inputs get
added into C++ linkstamp compile action. When set to true (defaults to false),
all inputs of relevant C++ linking action get added as inputs to the linkstamp
compile action too.
RELNOTES: None.
PiperOrigin-RevId: 187030217
|
|
|
|
| |
PiperOrigin-RevId: 187029559
|
|
|
|
| |
PiperOrigin-RevId: 187029004
|
|
|
|
| |
PiperOrigin-RevId: 187028864
|
|
|
|
| |
PiperOrigin-RevId: 187028110
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 187018017
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Stamped binaries now have a correct
build-data.properties file with regard to the
"Build time" field.
There's a mismatch in BuildInfo.BUILD_TIMESTAMP
semantics between Bazel and Google-internal Blaze:
Bazel assumes this amount is in milliseconds,
Blaze assumed seconds.
Since there are users depending on this field
already on both sides, it is too late to change
its semantics. So this commit only fixes the
bogus "Build time" field and leaves
BUILD_TIMESTAMP as milliseconds for Bazel and as
seconds for Blaze.
Fixes https://github.com/bazelbuild/bazel/issues/4469
Change-Id: I28282d660244af693ab16443ae1e42fb455f9dde
PiperOrigin-RevId: 187005016
|
|
|
|
| |
PiperOrigin-RevId: 186789569
|
|
|
|
| |
PiperOrigin-RevId: 186789093
|
|
|
|
|
|
| |
Fixes 4480.
RELNOTES: None.
PiperOrigin-RevId: 186774229
|
|
|
|
| |
PiperOrigin-RevId: 186772981
|
|
|
|
|
|
|
| |
Bazel because the test services APK is no longer installed by default as of unknown commit
RELNOTES: None.
PiperOrigin-RevId: 186772375
|
|
|
|
| |
PiperOrigin-RevId: 186765754
|
|
|
|
|
|
| |
SolibSymlinkAction.
PiperOrigin-RevId: 186765454
|
|
|
|
| |
PiperOrigin-RevId: 186765388
|
|
|
|
|
|
|
|
| |
Move dealing with coverage related features from CppConfiguration.configurationEnabledFeatures to CcCommon.configureFeatures.
Remove configurationEnabledFeatures.
RELNOTES: None.
PiperOrigin-RevId: 186744803
|
|
|
|
|
|
|
| |
constructor
RELNOTES: None.
PiperOrigin-RevId: 186744674
|
|
|
|
|
|
|
| |
android_local_test should not allow specifying resources and assets on the rule itself. If a user wants to add test specific resources/assets then they should wrap them in an android_library and add it to the deps of the android_local_test.
RELNOTES: None
PiperOrigin-RevId: 186724709
|
|
|
|
|
|
|
|
|
| |
consume binary resources.
This functionality is guarded by a flag, --experimental_android_local_test_binary_resources whose default value is false. If the flag is set to true, Bazel will generate the .ap_ and add the path to the .ap_ to the test_config.properties file. Bazel will still generate and pass the raw resources to Robolectric in both cases and so the cue to Robolectric that binary resources should be used is the presence of the path to the .ap_ in the test_config.properties file.
RELNOTES: None
PiperOrigin-RevId: 186708941
|
|
|
|
|
|
|
| |
android_local_test.
RELNOTES: None
PiperOrigin-RevId: 186699885
|
|
|
|
| |
PiperOrigin-RevId: 186691973
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 186679485
|
|
|
|
|
|
|
|
| |
These may be used to retrieve the ar and as programs associated with
the compiler toolchain.
RELNOTES: None.
PiperOrigin-RevId: 186626548
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 186623143
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 186617351
|
|
|
|
|
|
| |
CppLinkAction more suitable for serialization.
PiperOrigin-RevId: 186598828
|
|
|
|
|
|
|
|
|
|
|
| |
Linkstamps were not re-built when only volatile data changed, i.e. when we
modified cc_binary source, linkstamp was not recompiled so we got old
timestamps. The proper behavior is to recompile linkstamp whenever any input to
cc_binary linking action changes. And the implementation in this cl solves this
by adding all linking inputs as inputs to linkstamp compile action.
RELNOTES: None.
PiperOrigin-RevId: 186595143
|
|
|
|
|
|
|
| |
Fixes #3507.
RELNOTES: None.
PiperOrigin-RevId: 186595099
|
|
|
|
|
|
|
| |
Methods that return NestedSet shouldn't claim they may return duplicates or their return value will have any sort of meaningful order.
Change-Id: I98f92ec6ddbf4d35fea47b12bcd072bb1b0f1e43
PiperOrigin-RevId: 186585490
|
| |
|