| commit | 17c4c8bb0feaa0395b31757c8186521ec3c0d723 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@monogon.tech> | Tue Feb 01 12:59:47 2022 +0100 |
| committer | Lorenz Brun <lorenz@monogon.tech> | Tue Feb 08 13:06:05 2022 +0000 |
| tree | abcc2f8419659ac3f9dcb55a1c0c3de43f4008f0 | |
| parent | b6a9d3c613847de99be456f17c6b18cc4d1c4e63 [diff] |
m/n/b/fwprune: adapt to fsspec and use This modifies the fwprune tool to generate fsspecs instead of making copies and makes it take a list of paths for suffix matching instead of a directory as input. It also adds the fsspec_linux_firmware rule which uses the utility to actually build a partial fsspec. Finally it integrates the linux-firmware external repository and uses that rule to ship firmware in Metropolis. Change-Id: I0552995105eda84e63d7259040ad36d794079308 Reviewed-on: https://review.monogon.dev/c/monogon/+/534 Reviewed-by: Mateusz Zalega <mateusz@monogon.tech>
This is the main repository containing the source code for the Monogon Project.
This is pre-release software - feel free to look around, and check back later for our first release!
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 //...