| commit | 2fb13a89a00a1d0bf2e87f10516dcb5d7c0691dc | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Tue Feb 11 12:41:37 2020 +0100 |
| committer | Serge Bazanski <serge@nexantic.com> | Tue Feb 11 12:41:37 2020 +0100 |
| tree | 4a5c4b3b14afdd6d10192d2e6144d62051c92d9d | |
| parent | aa6b7346a87a5512fbdd5b39db766000c0e10415 [diff] |
third_party: slurp in edk2, kubernetes, mkfs.xfs This finishes the move from core/build/* into third_party/. While at first this might look like wasted bandwidth, this separation will make much more sense in the future, where different parts (not only the Smalltown core) might depend on shared external dependencies. In addition, having everything in third_party laid out in a similar fashion lends itself to writing more general rules. Already there is quite a bit of deduplicaiton that we could remove for reliability and readability. This does not fix the problem of the big honkin' genrule for mkfs.xfs - while I think we should fix it sooner than later by building a real toolchain, that time is not yet now. But at least we've moved things out of the way so that we can then drop in a better mkfs.xfs, once it is built so. Test Plan: build file mangling, CI should cover this X-Origin-Diff: phab/D391 GitOrigin-RevId: fb99c6a6270c5c6a56eeb4f18a41323ffebbc655
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.