| Age | Commit message (Collapse) | Author |
|---|
|
Those are a documented entry-point for the bootstrappable toolchain.
As such, they should be export targets, so the bootstrappable toolchain
can be used as an entirely absent repository.
|
|
This is handled similarly to the AR tool, i.e., provided from
binutils.
|
|
... and drop unneeded duplication as well as wrong expansion
variables in "PATH" fields.
|
|
|
|
The environment variable PATH is taken literally by the shell, without
any expansion. So, having a string like "$(TOOLCHAIN)/clang/bin"
in PATH does not change anything as we do not have a directory
with that name. Drop it for now. In the future we might add "bin
dirs" to the CC toolchain as well, but as long as our rules do not
support this, drop the wrong entry here.
|
|
|
|
|
|
Now that the rules-cc support toolchain definitions for the shell,
document the current status quo that the shell is (still) taken
from host.
|
|
An intended use case of this bootstrappable toolchain is to be
imported as toolchain into other projects. However, only export
targets should be imported into other projects (a recommendation
that is a requirement when obtaineing the imported project via a
serve endpoint). Fix this by exporting the toolchains.
|
|
... which not only requires "/bin" (for "sh") but also
"/usr/bin" for coreutils ("dirname", "realpath", "chmod",
etc.), which are needed for compiler wrappers and the patch
runner script.
|
|
|
