| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
| |
user_compile_flags
Also add magic to a feature named 'unfiltered_compile_flags' so the flags
expanded from it are not subject to nocopt filtering.
This is encore of https://github.com/bazelbuild/bazel/commit/268c0bcbf79f9f3f72d95fa51af0f1b18c5ce29e that was rolled back because it regressed
memory.
RELNOTES: None.
PiperOrigin-RevId: 167989075
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 167986260
|
|
|
|
|
|
|
|
| |
PlatformConfiguration is made a legal configuration fragment for every rule class.
Add a default "dummy" c++ toolchain to prevent resolution errors when legacy toolchain selection logic is used. Add toolchain mocks to java and shell tests.
PiperOrigin-RevId: 167901210
|
|
|
|
|
|
| |
RELNOTES: android_binary.nocompress_extensions now applies to all files in the
APK, not just resources and assets.
PiperOrigin-RevId: 167859686
|
|
|
|
|
|
| |
This is a prerequisite for merging the two interfaces.
PiperOrigin-RevId: 167843789
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is to help with the deprecation of said command line option; the
alternative is
java_runtime_suite(name="javabase", default=[":runtime"])
java_runtime(name="runtime", java_home=$(ABSOLUTE_JAVABASE)")
then running Blaze with the command line options
--javabase=<java_runtime_suite rule> --define=ABSOLUTE_JAVABASE=<path>
RELNOTES: None.
PiperOrigin-RevId: 167840565
|
|
|
|
| |
PiperOrigin-RevId: 167751263
|
|
|
|
|
|
|
| |
-classobfuscationdisctionry and -packageobfuscationdictionary arguments
RELNOTES: Make proguard_apply_dictionary also apply to class and package obfuscation, not just class members.
PiperOrigin-RevId: 167735831
|
|
|
|
|
|
|
|
|
| |
The resources attribute is being deprecated. Add a flag to disable it so we can
test impact locally and turn it off globally without waiting for a Bazel
release.
RELNOTES: none
PiperOrigin-RevId: 167717822
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
...or any other non repository rule.
Using a bind rule as the name of the repository was returning
a strange error "could not find handler for bind rule" which was
not useful, so was replaced by a crash.
Fixes #3664
Change-Id: Id0711470e6a1ab9267e05eb273900b18d0a27d6b
PiperOrigin-RevId: 167706825
|
|
|
|
|
|
|
|
|
| |
Split collect, concurrent, vfs, windows into package-level BUILD files.
Move clock classes out of "util", into their own Java package.
Move CompactHashSet into its own Java package to break a dependency cycle.
Give nestedset and inmemoryfs their own package-level BUILD files.
PiperOrigin-RevId: 167702127
|
|
|
|
| |
PiperOrigin-RevId: 167699728
|
|
|
|
|
|
| |
Fixes #3626.
PiperOrigin-RevId: 167687039
|
|
|
|
|
|
|
| |
organize the output tree of android_binary.
RELNOTES: None.
PiperOrigin-RevId: 167630660
|
|
|
|
|
|
|
|
|
|
| |
- require_defined_versions is deprecated and a no-op. A version must match existing defined versions if any exist
- default label must be present in versions labels if any are defined
- default label may not exist if no versions are defined
- when --xcode_version is specified on the command line, it must match a defined version if any are defined. If none are defined, this flag is a no-op
RELNOTES: None.
PiperOrigin-RevId: 167616628
|
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 167608048
|
|
|
|
|
|
|
|
|
|
| |
user_compile_flags
Also add magic to a feature named 'unfiltered_compile_flags' so the flags
expanded from it are not subject to nocopt filtering.
RELNOTES: None.
PiperOrigin-RevId: 167587189
|
|
|
|
|
|
| |
Closes #3673.
PiperOrigin-RevId: 167558706
|
|
|
|
|
|
|
|
|
| |
Also moves parenthetical remark to a completely different sentence, as
it seemed off where it was.
Closes #3657.
PiperOrigin-RevId: 167558504
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
aar_resources_extractor now supports long paths
on Windows.
If the script needs to extract a file from the
AAR where the destination path is too long, the
script will:
1. create a temporary junction under a short path,
pointing to the destination directory (which
has a long path)
2. extract the file under the junction
3. delete the junction and the temp directory
See https://github.com/bazelbuild/bazel/issues/3659
Change-Id: Ie85665b360a6514afaac546aaec8869224fe9d06
PiperOrigin-RevId: 167545085
|
|
|
|
|
|
|
| |
This removes our dependency on third_party/joda_time, which can be removed in the next commit.
Change-Id: Ibda131d34d0abdc2d675db4bfbd2e99480c055ee
PiperOrigin-RevId: 167515260
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 167505493
|
|
|
|
|
|
|
|
|
| |
host JAVA/JAVABASE attributes.
Also fix a few lint warnings and move a class so that it's closer to where it's actually used.
RELNOTES: None.
PiperOrigin-RevId: 167501208
|
|
|
|
|
|
|
|
|
| |
The only case this exception is thrown is when there is
a bug in Bazel and we should surface the whole stacktrace.
See #3664
PiperOrigin-RevId: 167492638
|
|
|
|
| |
PiperOrigin-RevId: 167480127
|
|
|
|
| |
PiperOrigin-RevId: 167477112
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke several tests in nightly.
[]
*** Original change description ***
Rollforward #2 of "AppleBinary and AppleStaticLibrary no longer propagate unwrapped ObjcProvider", after changes made to apple bazel rules to be compatible.
RELNOTES: None.
PiperOrigin-RevId: 167312716
|
|
|
|
|
|
|
|
|
|
|
| |
class.
TESTED=Dumped the actions graph for AndroidBinary before and after the change
and compared to make sure the same actions are registered, and also manually
invoked mobile-install.
RELNOTES: None.
PiperOrigin-RevId: 167311030
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bazel now creates all SpawnActions in
AndroidBinary, AndroidCommon, and DexArchiveAspect
such that they use the default shell environment.
The benefit of this is that these actions will
have a well-controlled, minimal environment, and
most importantly they'll have valid TMP and TEMP
environment variables, which is necessary for temp
file creaion on Windows.
I created this commit for the same reason as
https://github.com/bazelbuild/bazel/commit/0abf5fa2d64c76def5a8fa0f960b73ce0566af4d
See https://github.com/bazelbuild/bazel/issues/3659
Change-Id: Ice42ea6424af8984d3c382ab01727e04cbd0c1b4
PiperOrigin-RevId: 167285724
|
|
|
|
|
|
|
| |
Instead of passing all the runtime jars in the environment variable, we now write them all to a file and store the file path in the env variable, jacoco runner reading the jars from there. Changes on Jacoco runner side are here: https://github.com/bazelbuild/bazel/commit/05418b33dd87d63e2653e594d462b2aedb0e22e5
RELNOTES: A new Java coverage implementation is available. Makes possible coverage for Skylark JVM rules.
PiperOrigin-RevId: 167248966
|
|
|
|
|
|
|
|
| |
This will be used to create thin skylark rules to allow for select() on provider values, with xcode_config_alias's XcodeProperties to be the first.
This is demonstrated in XcodeConfigTest.
RELNOTES: None.
PiperOrigin-RevId: 167204266
|
|
|
|
|
|
|
|
| |
This feature is opening up beyond just ConfigFeatureFlags, and so should not
be restricted.
RELNOTES: None.
PiperOrigin-RevId: 167195959
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks rules_go CI
*** Original change description ***
Bazel c++ rules depend on a c++ toolchain.
PiperOrigin-RevId: 167191667
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 167164919
|
|
|
|
| |
PiperOrigin-RevId: 167154793
|
|
|
|
| |
PiperOrigin-RevId: 167147239
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 167143657
|
|
|
|
|
|
|
| |
Add _'s in proto.transitivedescriptorsets
RELNOTES: none
PiperOrigin-RevId: 167139522
|
|
|
|
|
|
|
|
|
|
| |
- Move ProfilerInfo into a subpackage (it's not necessary for profiling, just for analyzing a profile).
- Make some fields in Profiler public for ProfileInfo.
- Mark Profiler as ThreadSafe; there's no cyclic dependency here.
This is based on ulfjack's microbazel patch series: https://github.com/ulfjack/bazel/commit/44553fcac0fc876784d8f48c2e577d8c999712de
PiperOrigin-RevId: 167121952
|
|
|
|
|
| |
RELNOTES: `JavaInfo` is a preferred alias to `java_common.provider`.
PiperOrigin-RevId: 167116971
|
|
|
|
|
|
|
| |
unwrapped ObjcProvider", after changes made to apple bazel rules to be compatible.
RELNOTES: None.
PiperOrigin-RevId: 167061765
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After this CL, if the feature_flags attribute of android_test or
android_binary is not set, no transition takes place when entering that
rule. This means that if it is depended upon by another test or binary, it
will use the enclosing test or binary's flags.
This permits users of feature flags to depend on non-users of feature flags.
The opposite is still not permitted. If a dep sets feature flags, then the
target depending on it must have the exact same feature flags set.
This way, all targets used in an android_test are built the same way, but
it's possible to interoperate with targets which are agnostic to feature
flags.
Note that "not set" is different from "set to the empty dictionary"; the
former reuses the definitions set higher up in the build graph, while the
latter clears all feature flag values and resets them to their defaults.
RELNOTES: None.
PiperOrigin-RevId: 167035122
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 167031992
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 167028314
|
|
|
|
|
|
|
| |
also, AppleConfiguration no longer throws NPE with invalid cpu.
RELNOTES: None.
PiperOrigin-RevId: 167013760
|
|
|
|
|
|
|
|
| |
The code in scheduleLtoBackendAction was attempting to construct the Artifact for a .dwo file when Fission is enabled by getting the related artifact via the ruleContext. This doesn't work for nativedeps files which have a shared _nativedeps/-relative library path, instead of being under the package directory.
Instead, compute the .dwo path the same way we do the ThinLTO imports and index file outputs, using the linkArtifactFactory.
PiperOrigin-RevId: 167002233
|
|
|
|
|
|
|
|
| |
with the new android_binary parameter "proguard_apply_dictionary".
RELNOTES[NEW]: android_binary now supports proguard_apply_dictionary to specify a custom dictionary to use for choosing names to obfuscate classes and members to.
PiperOrigin-RevId: 167000875
|
|
|
|
| |
PiperOrigin-RevId: 166966182
|
|
|
|
|
|
| |
that is accessible to the c++ rules.
PiperOrigin-RevId: 166934390
|
|
|
|
|
|
|
| |
it turns out these keys are still used by objc_framework, so cannot be removed.
RELNOTES: None.
PiperOrigin-RevId: 166895085
|