| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 208049281
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The old list was, in order:
- %workspace%/tools/bazel.rc (unless --nomaster_bazelrc)
- %binary_dir%/bazel.bazelrc (unless --nomaster_bazelrc)
- system rc, /etc/bazel.bazelrc or in %ProgramData% for Windows (unless --nomaster_bazelrc)
- the first of the following gets called the "user" bazelrc
- path passed by flag --bazelrc
- %workspace%/.bazelrc
- $HOME/.bazelrc
The new list is hopefully a bit more consistent, as:
- system rc (unless --nosystem_rc)
- workspace, %workspace%/.bazelrc (unless --noworkspace_rc)
- user, $HOME/.bazelrc (unless --nohome_rc)
- command-line provided, passed as --bazelrc or nothing if the flag is absent.
This list removes two less than useful locations, duplication in the Workspace directory, and the rc next to the bazel binary. This location made sense at Google but is generally nonsensical elsewhere so we are removing it. It also stops the user local rc file from being overriden by passing in a custom file in --bazelrc.
In both old and new, --ignore_all_rc_files disables all of the above.
For a transition period, any file that you would have loaded but was not read will cause a WARNING to be printed. If you want the old file to still be read without moving its location, you can always import it into one of the new standard locations, or create a symlink.
Closes #4502, except for cleanup to remove the warning after a transition period of 1 Bazel version has passed.
RELNOTES[INC]: New bazelrc file list.
PiperOrigin-RevId: 207189212
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
as a list, rather than as a single line (i.e., newline delimited rather than
space delimited).
Before:
SUBCOMMAND: # //src/main/java/com/google/devtools/build/lib:string_util [action 'Building src/main/java/com/google/devtools/build/lib/libstring_util.jar (2 source files) [for host]']
(cd /tmp/devbazel_output_base/execroot/io_bazel && \
exec env - \
LC_CTYPE=en_US.UTF-8 \
external/embedded_jdk/bin/java -XX:+UseParallelOldGC -XX:-CompactStrings '--add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.code=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.comp=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.main=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED' '--add-opens=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED' '--patch-module=java.compiler=external/bazel_tools/third_party/java/jdk/langtools/java_compiler.jar' '--patch-module=jdk.compiler=external/bazel_tools/third_party/java/jdk/langtools/jdk_compiler.jar' '--add-opens=java.base/java.nio=ALL-UNNAMED' -jar external/bazel_tools/tools/jdk/JavaBuilder_deploy.jar @bazel-out/host/bin/src/main/java/com/google/devtools/build/lib/libstring_util.jar-2.params)
After:
SUBCOMMAND: # //src/main/java/com/google/devtools/build/lib:string_util [action 'Building src/main/java/com/google/devtools/build/lib/libstring_util.jar (2 source files) [for host]']
(cd /tmp/devbazel_output_base/execroot/io_bazel && \
exec env - \
LC_CTYPE=en_US.UTF-8 \
external/embedded_jdk/bin/java \
-XX:+UseParallelOldGC \
-XX:-CompactStrings \
'--add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED' \
'--add-exports=jdk.compiler/com.sun.tools.javac.code=ALL-UNNAMED' \
'--add-exports=jdk.compiler/com.sun.tools.javac.comp=ALL-UNNAMED' \
'--add-exports=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED' \
'--add-exports=jdk.compiler/com.sun.tools.javac.main=ALL-UNNAMED' \
'--add-exports=jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED' \
'--add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED' \
'--add-opens=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED' \
'--patch-module=java.compiler=external/bazel_tools/third_party/java/jdk/langtools/java_compiler.jar' \
'--patch-module=jdk.compiler=external/bazel_tools/third_party/java/jdk/langtools/jdk_compiler.jar' \
'--add-opens=java.base/java.nio=ALL-UNNAMED' \
-jar \
external/bazel_tools/tools/jdk/JavaBuilder_deploy.jar \
@bazel-out/host/bin/src/main/java/com/google/devtools/build/lib/libstring_util.jar-2.params)
RELNOTES: --subcommands can now take a "pretty_print" value ("--subcommands=pretty_print") to print the
arguments of subcommands as a list for easier reading.
PiperOrigin-RevId: 206213009
|
|
|
|
|
|
|
|
|
|
| |
to avoid confusion between the LHS and RHS host_javabases.
The LHS --host_javabase option should be considered deprecated and will
eventually be removed.
RELNOTES: Rename the startup flag --host_javabase to --server_javabase to avoid confusion with the build flag --host_javabase
PiperOrigin-RevId: 206015757
|
|
|
|
|
|
|
| |
Fixes #5592.
RELNOTES: Deleting deprecated no-op flag --show_package_location
PiperOrigin-RevId: 205834069
|
|
|
|
| |
PiperOrigin-RevId: 205718853
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 203723885
|
|
|
|
|
|
|
| |
Deprecates the flag, though it continues to exist as a no-op so that users get a warning before errors.
RELNOTES: --noexpand_configs_in_place is deprecated.
PiperOrigin-RevId: 200572053
|
|
|
|
| |
PiperOrigin-RevId: 200410790
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 199503117
|
|
|
|
|
|
| |
For generic references to the C/C++ compiler, stop referring to it as "gcc", as other compilers are used frequently now.
PiperOrigin-RevId: 199244730
|
|
|
|
|
|
|
| |
Crosstool selection will be based solely on --cpu and --compiler options.
RELNOTES: Option --glibc is removed, toolchain selection relies solely on --cpu and --compiler options.
PiperOrigin-RevId: 199156131
|
|
|
|
|
|
|
| |
RELNOTES[INC]: Bazel now always runs binaries in with "bazel run" in
interactive mode. The "--nodirect_run" command line option is now a no-op.
PiperOrigin-RevId: 197121535
|
|
|
|
|
|
|
|
| |
Fix a typo in option name
Closes #4927.
PiperOrigin-RevId: 196964791
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 196837438
|
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel/commit/e52c8418d37e902237c6676d06fcb4cad7fc4766.
RELNOTES: None.
PiperOrigin-RevId: 194240434
|
|
|
|
| |
PiperOrigin-RevId: 190256860
|
|
|
|
| |
PiperOrigin-RevId: 189201051
|
|
|
|
|
|
|
| |
It is no longer meaningful since the vfs doesn't have an internal path tree to dump.
RELNOTES: Remove support for blaze dump --vfs. It is no longer meaningful.
PiperOrigin-RevId: 188739379
|
|
|
|
| |
PiperOrigin-RevId: 188362796
|
|
|
|
|
|
| |
Closes #4689.
PiperOrigin-RevId: 188169719
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 187834884
|
|
|
|
|
|
|
|
| |
This option was removed in https://github.com/bazelbuild/bazel/commit/2ea4fa26281175c316651ec50784b820a9f409cf.
Closes #4509.
PiperOrigin-RevId: 186311923
|
|
|
|
|
|
|
|
|
|
|
| |
It seems that we still need to touch a file named `WORKSPACE`
```
ERROR: The 'build' command is only supported from within a workspace.
```
Closes #4539.
PiperOrigin-RevId: 185807230
|
|
|
|
|
|
|
|
| |
The docs failed to mention the expected name of the file next to the binary. Also missing was the information that these files do not override each other; they are always loaded if present.
Closes #4451.
PiperOrigin-RevId: 185805289
|
|
|
|
|
|
|
|
|
| |
Add docs for the --workspace_status_command flag.
Fixes https://github.com/bazelbuild/bazel/issues/4220
RELNOTES: none
PiperOrigin-RevId: 184492241
|
|
|
|
|
|
|
| |
This option has no effect, so don't give documentation readers false hope.
Change-Id: Ibbc0d2f62375fd146fedaa113a39027bd7d65d6c
PiperOrigin-RevId: 183240947
|
|
|
|
|
|
| |
Closes #4490.
PiperOrigin-RevId: 182812418
|
|
|
|
|
|
|
|
| |
s/statup/startup/
Closes #4274.
PiperOrigin-RevId: 178880672
|
|
|
|
|
|
|
| |
We don't put the toolchain identifier in directory names anymore.
RELNOTES: None.
PiperOrigin-RevId: 178229693
|
|
|
|
|
|
|
|
| |
Sounds a bit more neutral than either the username of an actual person (Ulf, in
this case) or the abbreviation for "J. Random Luser".
RELNOTES: None.
PiperOrigin-RevId: 178224013
|
|
|
|
|
| |
RELNOTES: Document startup option --host_javabase
PiperOrigin-RevId: 177849387
|
|
|
|
|
|
|
| |
Previously, they were in the Error checking options section, which doesn't seem correct.
Change-Id: I1306da91cff01157963d56db267188bda7d57d4f
PiperOrigin-RevId: 177835450
|
|
|
|
|
|
|
|
| |
Flag is mobile-insall v1 only, and has not been used in the last 30 days.
This change is a NOP since the default value in //third_party/bazel/tools/android/incremental_install.py is 2.
RELNOTES: None
PiperOrigin-RevId: 177536782
|
|
|
|
|
|
|
| |
Update the docs for clarity and to explain the --expand_configs_in_place alternate expansion behavior.
RELNOTES: None.
PiperOrigin-RevId: 177183524
|
|
|
|
|
|
|
|
| |
And adjust macOS name
Closes #4019.
PiperOrigin-RevId: 176665076
|
|
|
|
| |
PiperOrigin-RevId: 175718465
|
|
|
|
|
|
|
|
|
|
|
| |
It was added long ago, for reasons which are no longer relevant or
useful.
Also remove the build variable it controlled ("skip_mostly_static")
from CROSSTOOL files.
RELNOTES: None.
PiperOrigin-RevId: 175325225
|
|
|
|
|
|
| |
Now with more accuracy.
PiperOrigin-RevId: 174873635
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
This doesn't seem to be correct. I was confused by an example where a target is excluded from being run, but still built.
*** Original change description ***
RELNOTES: Document interaction between test_suite and target exclusions
PiperOrigin-RevId: 174536378
|
|
|
|
| |
PiperOrigin-RevId: 174027015
|
|
|
|
| |
PiperOrigin-RevId: 173955012
|
|
|
|
|
| |
RELNOTES: Document --host_javabase, --host_java_toolchain
PiperOrigin-RevId: 173945684
|
|
|
|
| |
PiperOrigin-RevId: 173466491
|
|
|
|
|
|
|
|
|
|
|
| |
This adds two dump command, bazel dump --rules and bazel dump --skylark_memory.
dump --rules outputs a summary of the count, action count, and memory consumption of each rule and aspect class.
dump --skylark_memory outputs a pprof-compatible file with all Skylark analysis allocations. Users can then use pprof as per normal to analyse their builds.
RELNOTES: Add memory profiler.
PiperOrigin-RevId: 172558600
|
|
|
|
|
|
| |
The dump command is readily available from bazel, so I don't see why the docs should be closed.
PiperOrigin-RevId: 171904287
|
|
|
|
| |
PiperOrigin-RevId: 169710801
|
|
PiperOrigin-RevId: 167477112
|