| commit | 5d40c67126d51ab1d78f44f51ec23cb75e9887fc | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@monogon.tech> | Tue Sep 28 15:06:37 2021 +0200 |
| committer | Lorenz Brun <lorenz@monogon.tech> | Thu Sep 30 13:14:43 2021 +0000 |
| tree | 9158b3c5c4a922c3e8759923c52a136ac206c229 | |
| parent | 296bde209e76f677dc0f38d003a27df83bcf0f5a [diff] |
third_party/efistub: init Adds the EFI stub from systemd-boot, built using our new EFI toolchain. This allows us to bundle kernels, command lines and other data into single EFI payloads and also sign them later. A rules to build these unified EFI payloads is coming later. Change-Id: I789e893ff88541f3dc9e7400ccd2565ae414e554 Reviewed-on: https://review.monogon.dev/c/monogon/+/335 Reviewed-by: Sergiusz Bazanski <serge@monogon.tech>
This is the main repository containing the source code for the Monogon Project.
⚠️ This is pre-release software that happens to be publicly available. Nothing to see here, please move along.
Our build environment requires a working Podman binary (your distribution should have one).
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, which enables full autocompletion for external dependencies and generated code. 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. On IntelliJ 2020.3 or later, you need to install a beta release of the plugin.
Add the absolute path to your ~/.cache/bazel-monogon folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-monogon
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.
Launch the node:
scripts/bin/bazel run //:launch
Run a kubectl command:
scripts/bin/bazel run //metropolis/cli/dbg -- kubectl describe
Run tests:
scripts/bin/bazel test //...