| commit | d3ce0ac027b205b1eeccbbcb062c9d417e205df4 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@monogon.tech> | Thu Mar 03 12:51:21 2022 +0100 |
| committer | Lorenz Brun <lorenz@monogon.tech> | Tue Mar 08 11:52:07 2022 +0000 |
| tree | b026e8c1b1d327531a739449b383ad21f8fd9c20 | |
| parent | 304d42c86f034386a957eaec36b0d254aef8dc76 [diff] |
m/n/b/fwprune: process links from metadata file The linux-firmware repository has a metadata file called WHENCE which contains mostly license and origin information, but critically it also contains data for symbolic links which are not materialized inside the repo itself. So we need to parse that file and create these symlinks ourselves. Change-Id: I9e6973e60d6f06e844dc879f658c9dd1913c432d Reviewed-on: https://review.monogon.dev/c/monogon/+/555 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 //...