-
Updated
Dec 29, 2020 - JavaScript
build-system
Here are 441 public repositories matching this topic...
-
Updated
Nov 11, 2020 - Go
-
Updated
Dec 30, 2020 - C++
-
Updated
Mar 2, 2020 - Go
-
Updated
Nov 4, 2020 - Python
-
Updated
Dec 29, 2020 - Python
-
Updated
Dec 31, 2020 - Scala
We're moving in the direction of Pants no longer registering all of its plugins by default and instead requiring users to opt-in. For example, you must explicitly opt in to pants.backend.python.lint.isort in V2, whereas V1 has pants.backend.python activated by default.
However, there is no good way to discover the possible backends outside of looking at the source code for this project.
One of the consumers of our system uses curly braces for content replacement in strings.
Due to the way that SD currently uses curly braces in the build process there is no way I can have a string that includes the braces for consumption.
I have tried a number of ways to escape the braces with no luck
Other languages and templating systems seem to use the concept of using double curly b
-
Updated
Dec 30, 2020 - Go
-
Updated
Dec 24, 2020 - C++
-
Updated
Dec 8, 2020 - Rust
Kudu plugin
-
Updated
Oct 22, 2020 - Dockerfile
-
Updated
Dec 7, 2020
-
Updated
Dec 11, 2020 - JavaScript
-
Updated
Dec 7, 2020 - Makefile
-
Updated
May 28, 2018 - Scala
-
Updated
Dec 19, 2020 - C
-
Updated
Dec 27, 2020 - C
-
Updated
Dec 12, 2020 - CMake
-
Updated
Jan 1, 2021 - Makefile
-
Updated
Mar 3, 2020 - Python
-
Updated
Mar 25, 2013 - CoffeeScript
Is your feature request related to a problem? Please describe.
Running any bazel build command on a fresh system with no Python, within a workspace that uses rules_haskell, will eventually yield an error of the form:
Repository rule _config_python3_toolchain defined at:
/root/.cache/bazel/_bazel_root/abad448bf464eefeaf2734c3cc8cdd46/external/rules_haskell/haskell/ghc_bindist.bzl:59
-
Updated
Dec 31, 2020 - Python
Improve this page
Add a description, image, and links to the build-system topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the build-system topic, visit your repo's landing page and select "manage topics."


If you use aquery_differ to diff 2 aquery proto files and you pass both
--attrs=inputsand--attrs=cmdline, if there is a difference in the Environment keys of actions it will not appear in the final diff