diff --git a/6.5.0/community/roadmaps-build-api.mdx b/6.5.0/community/roadmaps-build-api.mdx index dc05908..b0ee61c 100644 --- a/6.5.0/community/roadmaps-build-api.mdx +++ b/6.5.0/community/roadmaps-build-api.mdx @@ -1,4 +1,4 @@ - + */} --- title: 'Bazel Build API 2021 Roadmap' --- @@ -53,14 +53,14 @@ the particular language. Remove language specific logic from Bazel’s core. The Java rules will first be rewritten to Starlark and tested internally on a large code-base. After that they will be released to Bazel. -
-Q1 2021 +  +**Q1 2021** * Improve the **Java sandwich**, making it possible to rewrite existing Java rules. DONE -
-Q2 2021 +  +**Q2 2021** * Improve Starlark support for **native libraries** in Java. IN PROGRESS @@ -70,21 +70,21 @@ large code-base. After that they will be released to Bazel. * **java_library** rule is Starlarkified. IN PROGRESS -
-Mid 2021 +  +**Mid 2021** * **java_binary and java_test** rules are Starlarkified. * **java_import and java_plugin** rules are Starlarkified. -
-Fall 2021 +  +**Fall 2021** * Starlarkification of **java_\*_proto_library** * Remaining java rules are Starlarkified: **java_package_configuration, java_runtime, java_toolchain**. -
-2022 +  +**2022** * Starlarkification of **java_common module**. @@ -95,30 +95,30 @@ After that the C++ rules will be rewritten to Starlark piece by piece using builtins functionality. The API for C++ rules will not be made accessible from .bzl files until cc_module is rewritten in Starlark as well. -
-Q1 2021 +  +**Q1 2021** -* **Clang modules** support, DROPPED* +* **Clang modules** support, DROPPED * and **Include scanning** support, expected performance improvements from - both DROPPED* + both DROPPED * *We need more data to evaluate whether modules are really what is needed to improve performance. -
-Q2 2021 +  +**Q2 2021** * Internal **Go rules** are Starlarkified IN PROGRESS * Objective-C rules **objc_library and objc_import** and native code related to them are Starlarkified IN PROGRESS -
-Fall 2021 and beginning 2022 +  +**Fall 2021 and beginning 2022** * **cc_binary, cc_test and cc_library** are Starlarkified -
-2022 +  +**2022** * Starlarkification of other C++ rules (**fdo_profile, cc_import, cc_toolchain, cc_toolchain_suite, fdo_prefetch_hints, cc_toolchain_alias, @@ -127,8 +127,8 @@ builtins functionality. The API for C++ rules will not be made accessible from ## Misc -
-Mid 2021 +  +**Mid 2021** * Aspect can propagate other aspects - proposal [Aspects Propagating Other Aspects](https://docs.google.com/document/d/1fVNyskIgMoiNeOOGt57LdDmEkAShkYUKYQTkf5yD1fA/edit). diff --git a/6.5.0/external/advanced.mdx b/6.5.0/external/advanced.mdx index d468d5d..755ca43 100644 --- a/6.5.0/external/advanced.mdx +++ b/6.5.0/external/advanced.mdx @@ -43,7 +43,7 @@ http_archive( ) ``` -B/WORKSPACE {# This is not a buganizer link okay?? #} +B/WORKSPACE {/* This is not a buganizer link okay?? */} ```python workspace(name = "B") diff --git a/6.5.0/query/cquery.mdx b/6.5.0/query/cquery.mdx index 17a924b..657c83f 100644 --- a/6.5.0/query/cquery.mdx +++ b/6.5.0/query/cquery.mdx @@ -533,7 +533,7 @@ different niches. Consider the following to decide which is right for you: that `query` avoids. For example, if `"//foo"` exists in two configurations, which one should `cquery "deps(//foo)"` use? - The `[config](#config)` function can help with this. + The `[config](#config)` function can help with this. * As a newer tool, `cquery` lacks support for certain use cases. See [Known issues](#known-issues) for details. diff --git a/7.6.1/external/advanced.mdx b/7.6.1/external/advanced.mdx index 26ece4d..01a23ed 100644 --- a/7.6.1/external/advanced.mdx +++ b/7.6.1/external/advanced.mdx @@ -43,7 +43,7 @@ http_archive( ) ``` -B/WORKSPACE {# This is not a buganizer link okay?? #} +B/WORKSPACE {/* This is not a buganizer link okay?? */} ```python workspace(name = "B") diff --git a/8.0.1/external/advanced.mdx b/8.0.1/external/advanced.mdx index 26ece4d..01a23ed 100644 --- a/8.0.1/external/advanced.mdx +++ b/8.0.1/external/advanced.mdx @@ -43,7 +43,7 @@ http_archive( ) ``` -B/WORKSPACE {# This is not a buganizer link okay?? #} +B/WORKSPACE {/* This is not a buganizer link okay?? */} ```python workspace(name = "B") diff --git a/8.1.1/external/advanced.mdx b/8.1.1/external/advanced.mdx index 26ece4d..01a23ed 100644 --- a/8.1.1/external/advanced.mdx +++ b/8.1.1/external/advanced.mdx @@ -43,7 +43,7 @@ http_archive( ) ``` -B/WORKSPACE {# This is not a buganizer link okay?? #} +B/WORKSPACE {/* This is not a buganizer link okay?? */} ```python workspace(name = "B") diff --git a/8.2.1/external/advanced.mdx b/8.2.1/external/advanced.mdx index 26ece4d..01a23ed 100644 --- a/8.2.1/external/advanced.mdx +++ b/8.2.1/external/advanced.mdx @@ -43,7 +43,7 @@ http_archive( ) ``` -B/WORKSPACE {# This is not a buganizer link okay?? #} +B/WORKSPACE {/* This is not a buganizer link okay?? */} ```python workspace(name = "B") diff --git a/8.3.1/external/advanced.mdx b/8.3.1/external/advanced.mdx index 26ece4d..01a23ed 100644 --- a/8.3.1/external/advanced.mdx +++ b/8.3.1/external/advanced.mdx @@ -43,7 +43,7 @@ http_archive( ) ``` -B/WORKSPACE {# This is not a buganizer link okay?? #} +B/WORKSPACE {/* This is not a buganizer link okay?? */} ```python workspace(name = "B") diff --git a/8.4.2/external/advanced.mdx b/8.4.2/external/advanced.mdx index 26ece4d..01a23ed 100644 --- a/8.4.2/external/advanced.mdx +++ b/8.4.2/external/advanced.mdx @@ -43,7 +43,7 @@ http_archive( ) ``` -B/WORKSPACE {# This is not a buganizer link okay?? #} +B/WORKSPACE {/* This is not a buganizer link okay?? */} ```python workspace(name = "B") diff --git a/reference/be/functions.mdx b/reference/be/functions.mdx index 4f18f06..0a99e74 100644 --- a/reference/be/functions.mdx +++ b/reference/be/functions.mdx @@ -533,7 +533,7 @@ that counts the number of lines in the file. name = "count_lines_" + f[:-3], # strip ".cc" srcs = [f], outs = ["%s-linecount.txt" % f[:-3]], - cmd = "wc -l $< >$@", + cmd = "wc -l $< >$@", ) for f in glob(["*_test.cc"])] ``` @@ -614,10 +614,7 @@ Notes: is left out, some other rule must match to avoid an error. - `select` can be embedded _inside_ a larger - attribute assignment. So `srcs = ["common.sh"] - + select({ ":conditionA": ["myrule_a.sh"], ...})` and ` - srcs = select({ ":conditionA": ["a.sh"]}) + select({ ":conditionB": - ["b.sh"]})` are valid expressions. + attribute assignment. So `srcs = ["common.sh"] + select({":conditionA": ["myrule_a.sh"], ...})` and `srcs = select({":conditionA": ["a.sh"]}) + select({":conditionB": ["b.sh"]})` are valid expressions. - `select` works with most, but not all, attributes. Incompatible attributes are marked `nonconfigurable` in their documentation. diff --git a/reference/be/platforms-and-toolchains.mdx b/reference/be/platforms-and-toolchains.mdx index 1844b00..4e8e42e 100644 --- a/reference/be/platforms-and-toolchains.mdx +++ b/reference/be/platforms-and-toolchains.mdx @@ -229,7 +229,7 @@ is a parent platform: `remote_execution_properties` will be used. 2. If `remote_execution_property` is set on the child platform, and contains the - literal string {PARENT\_REMOTE\_EXECUTION\_PROPERTIES}, that macro will be + literal string `{PARENT\_REMOTE\_EXECUTION\_PROPERTIES}`, that macro will be replaced with the contents of the parent's `remote_execution_property` attribute. 3. If `remote_execution_property` is set on the child platform, and does not contain @@ -360,7 +360,7 @@ cpu architecture to be both `@platforms//cpu:x86_64` and `exec_properties` -Dictionary: String -> String; [nonconfigurable](common-definitions.html#configurable-attributes); default is `{}` +Dictionary: `String -> String`; [nonconfigurable](common-definitions.html#configurable-attributes); default is `{}` A map of strings that affect the way actions are executed remotely. Bazel makes no attempt to interpret this, it is treated as opaque data that's forwarded via the Platform field of @@ -407,7 +407,7 @@ String; [nonconfigurable](common-definitions.html#configurable-attributes); defa A string used to configure a remote execution platform. Actual builds make no attempt to interpret this, it is treated as opaque data that can be used by a specific SpawnRunner. This can include data from the parent platform's "remote\_execution\_properties" attribute, - by using the macro "{PARENT\_REMOTE\_EXECUTION\_PROPERTIES}". See the section on + by using the macro `"{PARENT\_REMOTE\_EXECUTION\_PROPERTIES}"`. See the section on [Platform Inheritance](#platform_inheritance) for details. `required_settings` diff --git a/reference/command-line-reference.mdx b/reference/command-line-reference.mdx index 73ed4cc..da735e0 100644 --- a/reference/command-line-reference.mdx +++ b/reference/command-line-reference.mdx @@ -5,14 +5,14 @@ title: 'Command-Line Reference' ``` -bazel [] [] +bazel [] `` [``] ``` or ``` -bazel [] [] -- [] +bazel [] `` [``] -- [] ``` @@ -25,8 +25,8 @@ Options can be passed to Bazel in different ways. Options that require a value can be passed with either an equals sign or a space: ``` ---