| commit | 140bddcbe1aac46b168f6fc2178eb9c3870a434c | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Fri Jun 05 21:01:19 2020 +0200 |
| committer | Serge Bazanski <serge@nexantic.com> | Fri Jun 05 21:01:19 2020 +0200 |
| tree | 8719383a79e42b1334a53f88bdc015872cba66dd | |
| parent | e6030f696613983ea00fc93b9e8b826cea7a1e9a [diff] |
core: build initramfs using generic initramfs rule This chips away at three different things: - it brings us closer to hermetic and cross-platform builds by not depending on genrule/shell and lz4-the-tool - it generalizes initramfs building (allowing for more than one to be built, if necessary) - sets the stage to use Bazel transitions [1] to force all included Go binaries to be built in pure/static mode while allowing host Go binaries to use cgo/dynamic linking if necessary, and hopefully also allowing us to get rid of some BUILD patches that set pure='on' in go_binary calls (notably needed in Cilium and some existing third_party dependencies). [1] - https://docs.bazel.build/versions/master/skylark/config.html#user-defined-transitions Test Plan: build machinery change, covered by existing tests X-Origin-Diff: phab/D554 GitOrigin-RevId: a5561eb5ca16e6529b9a4a2b98352f579c424222
This is the monorepo storing all of nexantic's internal projects and libraries.
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.
We check the entire .ijwb project directory into the repository, which requires everyone to use the latest version of both IntelliJ and the Bazel plugin, but eliminates manual setup steps.
The following steps are necessary:
Install Google's official 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.
Open the .ijwb folder as IntelliJ project.
Disable Vgo support for the project.
Run a non-incremental sync in IntelliJ
The plugin will automatically resolve paths for generated files.
If you do not use IntelliJ, you need to use the scripts/bazel_copy_generated_for_ide.sh script to copy files locally.