commit | 9e861a87775191faf1a027f603a0074446cd1319 | [log] [tgz] |
---|---|---|
author | Serge Bazanski <serge@nexantic.com> | Wed Sep 16 13:46:41 2020 +0200 |
committer | Serge Bazanski <serge@nexantic.com> | Wed Sep 16 13:46:41 2020 +0200 |
tree | 01fb624b542762594bad6e88d67c947263837769 | |
parent | 5faa2fc7fb6266486183fdc1455e711079d33e37 [diff] |
//build/toolchain/musl-host-gcc: implement This is a cc_toolchain which runs on x86 systems with Linux/gcc and targets Smalltown via static musl builds. It is currently unused, but can be tested by trying to build any cc_binary with --crosstool_top=//build/toolchain/musl-host-gcc:musl_host_cc_suite . Test Plan: This has been tested manually by running it against a simple cc_binary. Another revision on top of this will attempt to build mkfs.xfs with it. X-Origin-Diff: phab/D623 GitOrigin-RevId: ebdf51ee76d9d5a7fd94725c66ef53783f787df7
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)
Launch the node:
bazel run //:launch
Run a kubectl command:
bazel run //core/cmd/dbg -- kubectl describe
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.