| commit | df12522ed48dbac7edbae32be01a09770b01d0f7 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Sat May 23 00:29:30 2020 +0200 |
| committer | Serge Bazanski <serge@nexantic.com> | Sat May 23 00:29:30 2020 +0200 |
| tree | 167d9d5de66c430cc2ddd37feff561430ed0be5d | |
| parent | d3c59d22955d01ff4afcada9d4845cd935d820b7 [diff] |
*: unpin rules_go/gazelle We unpin these now that Gazelle 0.21.0 is out. This release also changes runfile pathnames for go_binary, so we have to fix up the test_boot.sh script that hardcodes a path. This also pulls in a new protobuf version, that we have to let in with its imperfections that nogo rightfully complains about. Test Plan: machinery change, current tests cover this X-Origin-Diff: phab/D538 GitOrigin-RevId: ad83d7868608b6883a891d127a6fbaf28f8aa14a
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.