| commit | 2e30e88fe6afcf06bdd01478bc584619e91d4c1b | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Wed Jun 24 15:17:29 2020 +0200 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Wed Jun 24 15:17:29 2020 +0200 |
| tree | c7e8a73330d170df708d8dc6de374d440411f224 | |
| parent | 5be29dda1d099e1d72636aec06bd3995f39ae4d8 [diff] |
Add our own qboot firmware My qboot fix (https://github.com/bonzini/qboot/pull/28) has (contrary to what I assumed based on the tests passing) not made it into QEMU yet, so the firmware shipped by it is still affected. This fix not being there silently broke our ktests since the return code processing can in weird conditions wrongly succeed. The fix for this will be another revision, same with code that actually uses this. This is just the build. Test Plan: Build test: `bazel build @com_github_bonzini_qboot//:qboot-bin`. Also tested in subsequent code depending on it. X-Origin-Diff: phab/D569 GitOrigin-RevId: b693220768bc8e39be21fd90eedc7ab79e9c4bcf
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.