This project is mirrored from https://github.com/bazelbuild/bazel.git.
Pull mirroring updated .
- Nov 06, 2024
-
-
Xùdōng Yáng authored
-
Googler authored
PiperOrigin-RevId: 693503398 Change-Id: I78c267e223ae64ab7fba81cdebc72a87bdba3782
-
Fabian Meumertzheim authored
This change patches the app manifest of the `java.exe` launcher in the embedded JDK to always use the UTF-8 codepage on Windows 1903 and later. This is necessary because the launcher sets sun.jnu.encoding to the system code page, which by default is a legacy code page such as Cp1252 on Windows. This causes the JVM to be unable to interact with files whose paths contain Unicode characters not representable in the system code page, as well as command-line arguments and environment variables containing such characters. The Windows VMs in CI are not running Windows 1903 or later yet, so this change can currently only be tested locally by running `bazel info character-encoding` and verifying that it prints `sun.jnu.encoding = UTF-8`. Work towards https://github.com/bazelbuild/bazel/issues/374 Work towards https://github.com/bazelbuild/bazel/issues/18293 Work towards https://github.com/bazelbuild/bazel/issues/23859 Closes #24172. PiperOrigin-RevId: 693466466 Change-Id: I4914c21e846493a8880ac8c6f5e1afa9fae87366
-
Googler authored
The BEP may now be configured to report files inline in the `TargetComplete` event on a per-output group basis, if the flag `--experimental_build_event_output_group_mode` is set appropriately. The `.proto` file references the correct flag name now. h/t to @sluongng for pointing out this discrepancy. RELNOTES: n/a PiperOrigin-RevId: 693463641 Change-Id: Ie0fec48a94ce665aeeaf0c46cf2bed88fd3fd6ba
-
Fabian Meumertzheim authored
This allows IDEs to query for the direct dependencies of the root module as well as how they can refer to them from the point of view of the root module. Also always emit `name` and `version` so that consumers don't have to know how to parse module keys. Work towards #22691 Closes #23787. PiperOrigin-RevId: 693453084 Change-Id: Ie3fd5e89301d8e83d0eaa686188634923853f01a
-
Googler authored
`//tools/cpp:toolchain_type`. PiperOrigin-RevId: 693392965 Change-Id: Ic6a3d3bad51574aeb4e15c6ab4f7d4416543c470
-
Googler authored
The critical path computation was recently reworked to query skyframe for the owning analysis node of an action that produced an input artifact to another action in some cases, but in analysis caching builds, the analysis node may be a deserialized analysis node and doesn't contain actions. For these cases, skip the action for critical path computation. PiperOrigin-RevId: 693363716 Change-Id: Iace4e723274807d5e69483b9841ac2f0aa0029b4
-
Googler authored
They are currently only used to acquire a lock on the output base, but a future change will use them to lock the install base as well. Human-readable output is also amended to refer to the "output base lock" instead of the "client lock", as the latter term becomes ambiguous once multiple locks exist. Progress on #2109. PiperOrigin-RevId: 693354279 Change-Id: I2b39e6f5ddb83bbc2be15a31d7de9655358776c5
-
- Nov 05, 2024
-
-
Googler authored
PiperOrigin-RevId: 693337121 Change-Id: Ieb601de778bc8359959cce52123c4d2e43973bed
-
Googler authored
On Unix we use a fcntl() lock, not flock(), and on Windows we use LockFileEx. PiperOrigin-RevId: 693314236 Change-Id: I6facfe2da1c2ece0bf75b6a815f73301e2db64b0
-
Googler authored
Cleanups in the wake of https://github.com/bazelbuild/bazel/commit/9c6d24f3f7595fc293415c8f60b05360a4ed8f85. RELNOTES: None. PiperOrigin-RevId: 693291109 Change-Id: Ia02b8d7495883e16fc3f021807fbca0015b3ad40
-
Googler authored
Closes #24143. PiperOrigin-RevId: 693275804 Change-Id: I052d7472beebafb1ca6c021ac4aafceb6b2aa6b7
-
Fabian Meumertzheim authored
Closes #24016. PiperOrigin-RevId: 693253221 Change-Id: I3c51ed1900bd3fa47a3448239389e57cb5505fa6
-
Lukacs T. Berki authored
This is accomplished by a new directive in REPO.bazel, "ignore_directories()". It takes a single argument, a list of directories to ignore and it allows the same wildcards as glob(). This is done separately from .bazelignore to provide a migration path off of that weird single-purpose configuration file. Implementing this requires splitting RepoFileFunction into two: a part that parses the repository file and one that creates a PackageArgs instance. This was necessary to avoid a Skyframe dependency cycle: when a WORKSPACE file is present and it loads a .bzl file from a repository with a REPO.bazel file, the repo mapping for the main repository depends on the WORKSPACE file, which depends on the .bzl file, which depends on the IgnoredPackagePrefixesValue of its repository, which then depends on the repo mapping of the main repository and the one the .bzl file is in, which then depend on the WORKSPACE file. Fixes #7093. RELNOTES[NEW]: REPO.bazel now allows another directive, "ignore_directories()". It takes a list of directories to ignore just like .bazelignore does, but with glob semantics. Closes #24032. PiperOrigin-RevId: 693227896 Change-Id: Ia3e02a2bfe9caf999fc641f75261b528b19c1d03
-
Fabian Meumertzheim authored
This unbreaks `toolchains_llvm`, which depends on this symbol. In the future, the new modular C++ toolchain API should make the symbol obsolete. Closes #24154. PiperOrigin-RevId: 693084632 Change-Id: Ica26f547c548fe3d25b3d57bdf2d432fd8f239ad
-
Googler authored
Matching the version with what Bazel is currently using and generating docs from. PiperOrigin-RevId: 692984290 Change-Id: I07cd096abd461be5374fe53e3ccf8d6b28e0181d
-
Googler authored
Currently, we rely on CreateFile to effectively obtain an exclusive (write) lock on the entire file, which makes the later call to LockFileEx redundant. This CL makes it so that we open the file in shared mode, and actually use LockFileEx to lock it. This makes a client-side lock compatible with a server-side one obtained through the JVM (which defaults to opening files in shared mode and uses LockFileEx for locking). Even though this doesn't matter for the output base lock, which is only ever obtained from the client side (the server side doesn't use filesystem-based locks), it will be necessary to implement install base locking (as part of fixing #2109). Note that this means an older Bazel might immediately exit instead of blocking for the lock, if the latter was previously acquired by a newer Bazel (since the older Bazel will always CreateFile successfully, but treat the subsequent LockFileEx failure as an unrecoverable error). However, this only matters during the very small window during which the client-side lock is held (it's taken over by the server-side lock in very short order), so I believe this is a very small price to pay to avoid adding more complexity. RELNOTES[INC]: On Windows, a change to the output base locking protocol might cause an older Bazel invoked immediately after a newer Bazel (on the same output base) to error out instead of blocking for the lock, even if --block_for_lock is enabled. PiperOrigin-RevId: 692973056 Change-Id: Iaf1ccecfb4c138333ec9d7a694b10caf96b2917b
-
- Nov 04, 2024
-
-
Googler authored
Compare with blaze_util_posix.cc. PiperOrigin-RevId: 692927012 Change-Id: Ibd7f44ec288c436e891157c82c1b5484c7e5c0f7
-
Googler authored
*** Reason for rollback *** Internal breakages *** Original change description *** Starlarkify objc/CompilationAttributes.java Closes #24009. PiperOrigin-RevId: 692916945 Change-Id: Idce0820a9e97e049a0568eb031594979de2b8b57
-
Googler authored
The links need to point into private package, where the rules are actually defined. Wrapper macros don't have docs. PiperOrigin-RevId: 692892068 Change-Id: I52c1153b59265a640aaceb8d6cf8a34c44967c2a
-
Farid Zakaria authored
Add support for when the AutoBazelRepository annotation is placed on a file in a root package (ie. one where there is no package) fixes #24150 Closes #24161. PiperOrigin-RevId: 692888334 Change-Id: Idd85e79250f64cf50ca709cf6ad8d025a0db032c
-
Googler authored
PiperOrigin-RevId: 692886072 Change-Id: I76690dd00b3633b9bd6cfac4fe0bf91bc302a77b
-
Googler authored
PiperOrigin-RevId: 692885000 Change-Id: I8f41cd60336a50ec4885c6119d7a9a80304a12f9
-
Keith Smiley authored
This allows passing through env in a similar way to doing `FOO=bar bazel run` but also allows you to put this in a `.bazelrc`, and allows you to bypass any environment filtering done when launching bazel. Closes #24068. PiperOrigin-RevId: 692853922 Change-Id: I802c31f2e0b30a738a41f24395dedbaf0b7caef1
-
- Nov 02, 2024
-
-
Googler authored
PiperOrigin-RevId: 692264816 Change-Id: I2803e0bbd11e6b134078aefaf611c28ecd213e37
-
Googler authored
PiperOrigin-RevId: 692257096 Change-Id: Ifa2253d40bbea1401f2b54d4f23b042d890c325a
-
Googler authored
Also quote conflicting flags in the error message. PiperOrigin-RevId: 692242271 Change-Id: Ibe7cb744ccfdb1c5a9cc34e67955ea3f7975c38e
-
Googler authored
Demonstrate the custom predicate by asserting on the number of evaluated keys. A parent key with an error dep is not evaluated if the dep is evaluated with `--nokeep_going`. On the other hand, a parent key with an error dep is evaluated if the dep is evaluated with `--keep_going`. PiperOrigin-RevId: 692223929 Change-Id: Id67244d9da7a241a8437fa89b8a517de526e0bf9
-
- Nov 01, 2024
-
-
Googler authored
PiperOrigin-RevId: 692176111 Change-Id: I7e23e8c8db9c65d6ed2f6cc22600f0bfdb1bf5d4
-
Googler authored
PiperOrigin-RevId: 692065957 Change-Id: Idcf89f4dcf6913460f920b06650b811ce391df58
-
Googler authored
Remove native stubs and builtin Proto rules, stop exporting them. Replace proto_library with filegroup in tests that are not concerned with Protos. Fix tests to use the implementation from @protobuf instead of mocked out rules. Fix ProtoInfo class to reference @protobuf. ProtoInfo is only used in test. Update protobuf to 29.0-rc2 and call protobuf_deps in WORKSPACE. python rules depend on rules_cc//cc/defs.bzl, that has a reference to protobuf. This makes workspace tests pass. PiperOrigin-RevId: 692063538 Change-Id: Ie5d055c9d326ca92dcf3f6ba7a02fb5dd7d1d63f
-
Googler authored
PiperOrigin-RevId: 691983613 Change-Id: I8801eab9c5faee440dd2a8b3384214352ecbec9f
-
Fabian Meumertzheim authored
Generate one synthetic "innate" module extension per repo rule class instead of a single one for all `use_repo_rule` usages in a given module. This avoids load cycles if one repo rule definition loads another one. Closes #24104. PiperOrigin-RevId: 691954099 Change-Id: Ia2eae6b6f45b169f364f1e83b76e8d907378329f
-
Googler authored
PiperOrigin-RevId: 691942287 Change-Id: Ib03b5732b6e411b8e66c5a2abe1d2bc95157f1e3
-
Googler authored
This keeps the testing up to date with the implementation and makes it possible to remove Sh rules. Add @rules_shell setup to Bazel analysis mock. Copy the implementation in BazelShTestConfiguredTarget. PiperOrigin-RevId: 691941360 Change-Id: I4300b4ce7d99526987e0043b347fb69090d4dd89
-
Googler authored
PiperOrigin-RevId: 691920217 Change-Id: I854c3a77404089ef806ff0c396803e5c2b313ad1
-
Googler authored
PiperOrigin-RevId: 691905697 Change-Id: I44ced76782c321c12e2775dec3688094ce6bcd80
-
Googler authored
PiperOrigin-RevId: 691899298 Change-Id: Ic70b6c9603b2c0b76df64f03d6c087ff4b7857e5
-
Googler authored
Split //tools, //tools/build_defs/hash, //tools/build_defs/pkg packages into 2 BUILD files. BUILD is used by Bazel only and BUILD.tools ends up in @bazel_tools. The split reduces the number of @rules_shell usages. PiperOrigin-RevId: 691898958 Change-Id: Ie95a0ba47fbdc3c183bf6f9154913675796657a6
-
Googler authored
This removes a reference to protobuf happening in some of the defs.bzl. PiperOrigin-RevId: 691854436 Change-Id: Ifae374725b62270ef532f57b6b646c4f8e287800
-