| commit | 385c12f84a0f1b6b5d70f228a0fb629f6f8f316c | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Wed Jun 17 12:12:42 2020 +0200 |
| committer | Serge Bazanski <serge@nexantic.com> | Wed Jun 17 12:12:42 2020 +0200 |
| tree | ef5ea6804ca0419e8851d1a21f956508764ba446 | |
| parent | 032ca1877adc3421343ed35a49c014ca261effff [diff] |
build/toolchain: init This adds a new, bare-bones, host-based C++ toolchain, and enables it for all target builds. This toolchain replaces the automatically generated host toolchain from bazel-tools, and differs in the following ways: - uses fully hardcoded paths - is the bare minimum required, which allows us full control over all aspects of it, notably link arguments - does not assume we're building normal C++ binaries for Linux (for instance, the new toolchain does not always link with -lm) This is in anticipation of a change by @lorenz that uses cc_binary to build qboot for tests. However, this is also a good basis to start writing a 'real' toolchain suite for mkfs.xfs, linux & co. Test Plan: For now, this is unused - but does not break any existing flow, which is fine. I did test this on a qboot WIP commit from @lorenz, and it at least fixed our immediate problem that it wanted to build it with with -lm,-lstdc++ - which we didn't. X-Origin-Diff: phab/D560 GitOrigin-RevId: 8a5bc5f00a0a0534ea245e556d160f5bab7f8a0c
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.