| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
|
|
|
|
| |
We pass the clientEnv to the workspace status command, and it may use
environment variables to influence status. We must therefore reevaluate
the workspace status command whenever the clientEnv changes.
Fixes #4222
Closes #4705.
PiperOrigin-RevId: 187988847
|
|
|
|
| |
PiperOrigin-RevId: 187986062
|
|
|
|
|
|
|
| |
This isn't strictly necessary since we disable caching and require local
execution.
PiperOrigin-RevId: 187985476
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 187974423
|
|
|
|
| |
PiperOrigin-RevId: 187956593
|
|
|
|
| |
PiperOrigin-RevId: 187945746
|
|
|
|
|
|
| |
multiple times.
PiperOrigin-RevId: 187941859
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 187936071
|
|
|
|
|
|
|
|
|
|
| |
This provides a io.grpc.ClientInterceptor implementation that can be used to log gRPC call information. The interceptor can select a logging handler to use based on the gRPC method being called (Watch, Execute, Write, etc) to build a LogEntry, which can then be logged after the call has finished. Unit tests for the interceptor are included.
In this change, the interceptor is never invoked, nor are there any handlers implemented for any gRPC methods. The interceptor also never tries to log any entries.
To avoid circular dependency issues (Remote library will depend on logger which depends on remote library for utils), I've factored out the utility classes from the remote library into their own directory/package as part of this change.
PiperOrigin-RevId: 187926516
|
|
|
|
|
|
| |
Needed for Attribute serialization.
PiperOrigin-RevId: 187907727
|
|
|
|
|
|
|
|
| |
This was broken by the jar being renamed from SingleJar_deploy.jar to bazel-singlejar_deploy.jar in commit 6705b508fe069147c853ca9669363342f3527689 (Fixes #3988)
Closes #4642.
PiperOrigin-RevId: 187880736
|
|
|
|
|
|
|
| |
actual toolchain, not the CppConfiguration.
Change-Id: I9cb74a883d3041ee2c31d294c0a1a36df578f738
PiperOrigin-RevId: 187880704
|
|
|
|
|
|
|
|
| |
The user manual filename has been renamed from `bazel-user-manual.html` to `user-manual.html`.
Closes #4662.
PiperOrigin-RevId: 187877241
|
|
|
|
|
|
|
|
| |
Previously, there was a risk of filename collisions, since all data files were flattened into the BUILD directory.
Closes #4747.
PiperOrigin-RevId: 187870196
|
|
|
|
|
|
| |
Closes #4743.
PiperOrigin-RevId: 187869648
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Fixed issue that led to rollback.
RELNOTES: None
*** Original change description ***
Automated rollback of commit eee53d3a33dde441f7e7adaecde81ef2d3db7c1b.
*** Reason for rollback ***
breaks Blaze_CorpTest
*** Original change description ***
@AutoCodec ConfiguredTargetValue.
PiperOrigin-RevId: 187869560
|
|
|
|
|
|
|
|
| |
Fixes #4740
Closes #4768.
PiperOrigin-RevId: 187868625
|
|
|
|
| |
PiperOrigin-RevId: 187868296
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 187865083
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Implement Runfiles::EnvVars so it's now possible
to propagate runfiles to subprocesses via
environment variables (RUNFILES_MANIFEST_FILE and
RUNFILES_DIR).
Subsequent commits will add more feataures:
- automatic Runfiles creation based on argv[0] and
the envvars of this process
See https://github.com/bazelbuild/bazel/issues/4460
Change-Id: If9a37b1be13b9cbacf21a496305d60444fd660b2
PiperOrigin-RevId: 187858830
|
|
|
|
|
|
|
|
| |
RELNOTES: None.
Closes #4710.
PiperOrigin-RevId: 187857722
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When this option is set to true, then bazel will not scan linkopts for -static
and will therefore never set linking mode to fully_static. This option will be
used to flip the switch once the world is migrated away from fully static
linking mode.
RELNOTES: C++: Introduced --experimental_drop_fully_static_linking_mode
Fully static linking mode will be removed soon. This option allows you to test
if your build will be passing.
Strategy for migrating away from fully static linking mode is to define a
crosstool feature named `fully_static_link`, enable it from the target (by
adding `features = [ "fully_static_link" ]`), and make sure the target is build
with `linkstatic = 1`. Buildozer command that will do just that is:
buildozer 'remove linkopts -static' 'set linkstatic 1' 'add features fully_static_link' //foo:bar
PiperOrigin-RevId: 187856775
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 187855919
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/bazel/android:android_ndk_integration_test
and
//src/test/shell/bazel:bazel_test_test
They're timing out on Kokoro recently.
RELNOTES: None
PiperOrigin-RevId: 187853786
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 187852219
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Link inputs are there only to invalidate the action, they don't affect the
execution of the compile action. This cl optimizes the action execution by not
having to collect unnecessary inputs into the sandbox.
Since this is CppCompileAction and nothing is easy here, let me elaborate on my
assumptions. The goal of this cl is to stop passing unneeded inputs into Spawns.
This is implemented by introducing a dispensableInputs field to the
CppCompileAction. SpawnGccStrategy then doesn't forward these further.
I'm not adding dispensableInputs to the ActionKey. I think it's enough to put
them to the inputs and into the updateActionInputs method.
RELNOTES: None.
PiperOrigin-RevId: 187849482
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 187849221
|
|
|
|
|
|
|
|
| |
cc-compiler-darwin depends on osx_wrapper and we should refer to it in dependencies. Otherwise only standalone builds will work.
Closes #3929.
PiperOrigin-RevId: 187846122
|
|
|
|
|
|
|
|
| |
The example for Depending on non-Bazel projects describes depending on a .so file. java_library builds .jar files, so is inconsistent.This PR switches the example to use cc_library, which actually builds a .so file so matches the description.
Closes #4745.
PiperOrigin-RevId: 187839898
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 187834884
|
|
|
|
|
|
|
|
|
|
| |
Update the documentation about:
- compiling Bazel from source (without an existing Bazel binary) on Windows
- OS and software requirements on Windows
Closes #4741.
PiperOrigin-RevId: 187829532
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
breaks Blaze_CorpTest
*** Original change description ***
@AutoCodec ConfiguredTargetValue.
PiperOrigin-RevId: 187783702
|
|
|
|
|
|
|
|
| |
ObjectCodec into a MEMOIZE_AFTER MemoizingCodec. I think that this is safe, because all the codecs that are being wrapped this way weren't memoizing anything internally that I could see.
In order to @AutoCodec the WithValue type, which is generic and can have null elements in lists, add functionality to @AutoCodec to deal with generic type static instantiators, matching generic type arguments (although I'm not sure why that wasn't already working), and null elements in lists.
PiperOrigin-RevId: 187740461
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 187734792
|
|
|
|
|
|
| |
RELNOTES:None.
PiperOrigin-RevId: 187711775
|
|
|
|
|
|
|
|
| |
doesn't save memory in the 32-bit case, but makes it easier for people to see how many SkyKeys we have.
There's some unnecessary interning in tests, but it was easier to copypasta and doesn't harm anything, I think.
PiperOrigin-RevId: 187694309
|
|
|
|
|
|
|
| |
the directory
RELNOTES: None.
PiperOrigin-RevId: 187692669
|
|
|
|
|
|
|
|
| |
The only two remaining users are for JAR, so directly call into BazelJavaBuilder rather than through our multiplex tool.
This requires opening the visibility of BazelJavaBuilder up to public.
PiperOrigin-RevId: 187690855
|
|
|
|
|
|
|
| |
published via the BEP, instead of only publishing failed actions and extra actions.
RELNOTES: Add a --build_event_publish_all_actions flag to allow all actions to be published via the BEP.
PiperOrigin-RevId: 187683799
|
|
|
|
|
|
| |
don't care about the group structure, and simplify the logic for prefetching old deps.
PiperOrigin-RevId: 187681887
|
|
|
|
|
|
| |
Needed for Attribute serialization.
PiperOrigin-RevId: 187676061
|
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 187671513
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 187671277
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Changelog: https://android.googlesource.com/platform/ndk/+/ndk-release-r16/CHANGELOG.md
> The deprecated headers have been removed. Unified Headers are now simply The Headers.
Support for this was added in r15.
> libc++ is out of beta and is now the preferred STL in the NDK. Starting in r17, libc++ is the default STL for CMake and standalone toolchains. If you manually selected a different STL, we strongly encourage you to move to libc++. For more details, see this blog post.
We bind the default `//external:android/crosstool` in AndroidNdkRepositoryRule before the repository function is evaluated, so changing the default STL will affect the older NDK revisions too. Until we have a new mechanism to specify the default crosstool, users will need to use `--android_crosstool_top=@androidndk//:toolchain-libcpp` to use `libc++`.
> GCC, armeabi, mips, mip64 are deprecated but still buildable/useable.
We can remove support for these in the r17 configuration.
There are no other actionable differences between r15 and r16, so we can reuse the r15 configuration for r16.
RELNOTES: Added Android NDK r16 support. Use --cxxopt='-std=c++11` compile with the C++11 standard, and `--android_crosstool_top=@androidndk//:toolchain-libcpp` to use the `libc++` STL.
Fixes https://github.com/bazelbuild/bazel/issues/4068
PiperOrigin-RevId: 187664390
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
NDK15 changelog:
https://android.googlesource.com/platform/ndk/+/ndk-r15-release/CHANGELOG.md
Notable changes for this CL:
- Clang has been updated to v5.0.300080.
- android-9 is not supported anymore. Anything lower than android-14 will default to android-14.
- NDK sysroot has been changed to %ndk%/sysroot
- Requires additional compilation flags because the headers are now unified in a single location across archs and API levels
Also removed NDK 10 checks in integration tests because it is old and we don't test against that anymore.
Fixes https://github.com/bazelbuild/bazel/issues/3137
Paves the way for r16: https://github.com/bazelbuild/bazel/issues/4068
RELNOTES[NEW]: Added Android NDK r15 support, including compatibility with Unified Headers.
PiperOrigin-RevId: 187648715
|
|
|
|
|
|
|
| |
Explain the deprecation of ctx.outputs.executable.
RELNOTES: None
PiperOrigin-RevId: 187640408
|
|
|
|
|
|
|
| |
Rewrite that part of rules.md and update rule() docs. Also clarify the Action object's docs to put it in context.
RELNOTES: None
PiperOrigin-RevId: 187636896
|
|
|
|
| |
PiperOrigin-RevId: 187635570
|
|
|
|
|
|
|
|
|
|
| |
Needed so that actions are properly invalidated and re-run when the platform's remote execution properties change.
Fixes #4756.
Closes #4728.
Change-Id: Ia227d110c10c9aad2164cefa8a90361cc4359332
PiperOrigin-RevId: 187621349
|
|
|
|
|
|
|
| |
crosstool top.
Change-Id: I531034b0c991d18b05818db4b40cbd739535b565
PiperOrigin-RevId: 187617580
|