| commit | 14cf750cac0d6c6e9504871246a45a226b2eb03e | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Thu May 28 14:29:56 2020 +0200 |
| committer | Serge Bazanski <serge@nexantic.com> | Thu May 28 14:29:56 2020 +0200 |
| tree | 5c17e5c6e9904675403e47f8a8658e966a9506b0 | |
| parent | f369cfa3ab4ad5ba882fa66f2fd1c3df8e5b4495 [diff] |
fietsje: implement .replace, add Cilium dependencies. The new .replace() can be used to mirror 'replace' stanzas in go.mod, and that's what it's being used for in Cilium, as it ships a handful of forked libraries that we have to pull in. The Cilium targets are currently unused, but the ones confirmed to build are: - @com_github_cilium_cilium//cilium: cilium API client - @com_github_cilium_cilium//daemon:daemon: cilium daemon/agent - @com_github_cilium_cilium//operator: cilium operator These currently built as dynamic libraries - turning them into static/pure builds will come in a later build. Test Plan: how do we test this? :) X-Origin-Diff: phab/D542 GitOrigin-RevId: b38c7c1d0be8b0b88ea8f6992c9c5557189399cc
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.