aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/docs/user-manual.html
Commit message (Collapse)AuthorAge
* Add minimal documentation for the new aquery command.Gravatar twerth2018-08-09
| | | | | RELNOTES: None PiperOrigin-RevId: 208049281
* Change the list of rc files accepted.Gravatar ccalvarin2018-08-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Modify --subcommands to allow pretty printing the arguments of a subcommandGravatar ahumesky2018-07-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Add a --server_javabase startup option as an alias for the LHS --host_javabaseGravatar cushon2018-07-25
| | | | | | | | | | 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
* Delete --show_package_location, which has been deprecated / no-op for years.Gravatar felly2018-07-24
| | | | | | | Fixes #5592. RELNOTES: Deleting deprecated no-op flag --show_package_location PiperOrigin-RevId: 205834069
* Make the docs for --javabase less misleadingGravatar cushon2018-07-23
| | | | PiperOrigin-RevId: 205718853
* Update Blaze user manual to mention the new blaze run behavior.Gravatar diamondm2018-07-09
| | | | | RELNOTES: None. PiperOrigin-RevId: 203723885
* Remove fixed point config expansion.Gravatar ccalvarin2018-06-14
| | | | | | | 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
* Add documentation on platform flags to the user manual.Gravatar jcater2018-06-13
| | | | PiperOrigin-RevId: 200410790
* Mark --batch as deprecated in the documentation.Gravatar ccalvarin2018-06-06
| | | | | RELNOTES: None. PiperOrigin-RevId: 199503117
* Update Blaze documentation to reflect that gcc is not the only compiler used.Gravatar Googler2018-06-04
| | | | | | For generic references to the C/C++ compiler, stop referring to it as "gcc", as other compilers are used frequently now. PiperOrigin-RevId: 199244730
* Remove --glibc optionGravatar rosica2018-06-04
| | | | | | | 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
* Remove "bazel run --nodirect_run".Gravatar lberki2018-05-18
| | | | | | | 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 typo in user manualGravatar Dmitry Petrashko2018-05-17
| | | | | | | | Fix a typo in option name Closes #4927. PiperOrigin-RevId: 196964791
* Make small readability improvements to Blaze user manual.Gravatar Googler2018-05-16
| | | | | RELNOTES: None. PiperOrigin-RevId: 196837438
* Update the documentation in the wake of ↵Gravatar lberki2018-04-25
| | | | | | | https://github.com/bazelbuild/bazel/commit/e52c8418d37e902237c6676d06fcb4cad7fc4766. RELNOTES: None. PiperOrigin-RevId: 194240434
* fix typo in blaze user manual.Gravatar juliexxia2018-03-23
| | | | PiperOrigin-RevId: 190256860
* Add cquery to Blaze manual's list of commandsGravatar juliexxia2018-03-15
| | | | PiperOrigin-RevId: 189201051
* Remove support for blaze dump --vfs.Gravatar tomlu2018-03-12
| | | | | | | 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
* Add missing "dump" command link from Bazel user manual.Gravatar gregce2018-03-08
| | | | PiperOrigin-RevId: 188362796
* Fixed left alignment in docGravatar Anders Sundman (asum)2018-03-07
| | | | | | Closes #4689. PiperOrigin-RevId: 188169719
* Add documentation for the action graph dump command.Gravatar twerth2018-03-05
| | | | | RELNOTES: None PiperOrigin-RevId: 187834884
* Docs: remove reference to supplying an absolute path to --javabase.Gravatar Gregg Donovan2018-02-20
| | | | | | | | This option was removed in https://github.com/bazelbuild/bazel/commit/2ea4fa26281175c316651ec50784b820a9f409cf. Closes #4509. PiperOrigin-RevId: 186311923
* docs : add `touch WORKSPACE`Gravatar Passw2018-02-15
| | | | | | | | | | | 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
* Provide a bit more information on the expected location of bazelrc files.Gravatar Sergio Campama2018-02-15
| | | | | | | | 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
* docs: document --workspace_status_commandGravatar laszlocsomor2018-02-05
| | | | | | | | | Add docs for the --workspace_status_command flag. Fixes https://github.com/bazelbuild/bazel/issues/4220 RELNOTES: none PiperOrigin-RevId: 184492241
* Delete documentation for --analysis_warnings_as_errors.Gravatar Benjamin Peterson2018-01-25
| | | | | | | This option has no effect, so don't give documentation readers false hope. Change-Id: Ibbc0d2f62375fd146fedaa113a39027bd7d65d6c PiperOrigin-RevId: 183240947
* Fixed docs: `bazel fetch` is not a required manual step before `bazel build`Gravatar Jingwen Chen2018-01-22
| | | | | | Closes #4490. PiperOrigin-RevId: 182812418
* Fix small typo in user manualGravatar Dave Rolsky2017-12-13
| | | | | | | | s/statup/startup/ Closes #4274. PiperOrigin-RevId: 178880672
* Remove toolchain identifier from blaze-out paths in documentation.Gravatar lberki2017-12-07
| | | | | | | We don't put the toolchain identifier in directory names anymore. RELNOTES: None. PiperOrigin-RevId: 178229693
* Replace fictional usernames with "johndoe".Gravatar lberki2017-12-07
| | | | | | | | 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
* Document the startup option --host_javabase.Gravatar Googler2017-12-04
| | | | | RELNOTES: Document startup option --host_javabase PiperOrigin-RevId: 177849387
* Move extra action flag docs into the Semantics section.Gravatar Benjamin Peterson2017-12-04
| | | | | | | Previously, they were in the Error checking options section, which doesn't seem correct. Change-Id: I1306da91cff01157963d56db267188bda7d57d4f PiperOrigin-RevId: 177835450
* Remove unused adb_jobs flag.Gravatar Googler2017-11-30
| | | | | | | | 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 blazerc documentation in the blaze/bazel user mannuals.Gravatar ccalvarin2017-11-28
| | | | | | | Update the docs for clarity and to explain the --expand_configs_in_place alternate expansion behavior. RELNOTES: None. PiperOrigin-RevId: 177183524
* Fix typo in `user-manual.html`Gravatar timm-gs2017-11-22
| | | | | | | | And adjust macOS name Closes #4019. PiperOrigin-RevId: 176665076
* Replace Container Engine references with Kubernetes Engine.Gravatar spomorski2017-11-14
| | | | PiperOrigin-RevId: 175718465
* Remove bazel's --experimental_skip_static_outputs option.Gravatar Googler2017-11-10
| | | | | | | | | | | 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
* RELNOTES: Document interaction between test_suite and target exclusionsGravatar Googler2017-11-07
| | | | | | Now with more accuracy. PiperOrigin-RevId: 174873635
* Automated rollback of commit 0dffc49f528c4c6e641221060e41aa6896310bdf.Gravatar Googler2017-11-06
| | | | | | | | | | | *** 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
* Correct mistake in blaze dump docs.Gravatar tomlu2017-10-31
| | | | PiperOrigin-RevId: 174027015
* Internal changeGravatar tomlu2017-10-31
| | | | PiperOrigin-RevId: 173955012
* Document --host_javabase, --host_java_toolchainGravatar cushon2017-10-31
| | | | | RELNOTES: Document --host_javabase, --host_java_toolchain PiperOrigin-RevId: 173945684
* RELNOTES: Document interaction between test_suite and target exclusionsGravatar Googler2017-10-26
| | | | PiperOrigin-RevId: 173466491
* Add memory profiler.Gravatar tomlu2017-10-18
| | | | | | | | | | | 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
* Make blaze dump docs external.Gravatar tomlu2017-10-12
| | | | | | The dump command is readily available from bazel, so I don't see why the docs should be closed. PiperOrigin-RevId: 171904287
* Update doc: there is no default value for --jobs.Gravatar Googler2017-09-25
| | | | PiperOrigin-RevId: 169710801
* Rename bazel-user-manual.html into user-manual.htmlGravatar dmarting2017-09-04
PiperOrigin-RevId: 167477112
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-15 22:31:58 +0000