| commit | bb95ebd12f8777b1b653653bcb54a081b6c54771 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Tue Mar 16 15:06:51 2021 +0100 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Tue Mar 16 15:06:51 2021 +0100 |
| tree | 0c52fbe31ea06cf4b1151e991f3da4ed6515b426 | |
| parent | b60d9cb51462a82a89f9c16f5ca6b4541de6d450 [diff] |
Include compiler-specific headers in musl toolchain sysroot Currently our musl sysroot does not include any compiler-specific headers. This makes the musl toolchain unable to build more complicated things like QEMU. Since the musl toolchain is not actually a real toolchain, but just a thin wrapper around the host toolchain this is a problem as these headers are not static. For a lack of better options it has thus been decided that we're just going to manually merge the headers for our build container in. This is expected to be removed as soon as we have a proper toolchain. Test Plan: Tested in subsequent revision X-Origin-Diff: phab/D737 GitOrigin-RevId: a1ed1d229c87980341c80b22263f5d9a4cf9924c
This is the main repository containing Monogon's public source code, including Metropolis.
We assume a Fedora host system provisioned using rW, and IntelliJ as the IDE.
For better reproducibility, all builds are executed in containers.
Spinning up: scripts/create_container.sh
Spinning down: scripts/destroy_container.sh
Running commands: scripts/run_in_container.sh <...>
Using bazel using a wrapper script: scripts/bin/bazel <...> (add to your local $PATH for convenience)
This repository is compatible with the IntelliJ Bazel plugin. All commands run inside the container, and necessary paths are mapped into the container.
The following steps are necessary:
Install Google's Bazel plugin in IntelliJ.
Add the absolute path to your ~/.cache/bazel-nxt folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-nxt
Set "Bazel Binary Location" in Other Settings → Bazel Settings to the absolute path of scripts/bin/bazel. This is a wrapper that will execute Bazel inside the container.
Use File → Import Bazel project... to create a new project from .bazelproject.
After running the first sync, everything should now resolve in the IDE, including generated code.
It's strongly recommend to use our project presets for file watchers and other IDE features. Run this command and re-open the project in order to install them:
bazel run intellij/localconfig $(pwd)
Launch the node:
bazel run //:launch
Run a kubectl command:
bazel run //metropolis/cli/dbg -- kubectl describe