| commit | 7b5d994379ef72ccf9f4de15d01b9604fc650287 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Thu Mar 19 16:14:02 2020 +0100 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Thu Mar 19 16:14:02 2020 +0100 |
| tree | baaa1bb99c2cb3e081d4f978303be56520a3e4df | |
| parent | 9374393a16b9400866003cd972f9c4711c94869c [diff] |
Update rules_go to 0.22.1 to fix @go_googleapis issue This fixes a known issue[1] with rules_go in combination with Bazel 2.2+ and some protobuf generates (like @go_googleapis). Also updates a few dependencies because rules_go switched to a newer GRPC compiler. [1] https://github.com/bazelbuild/bazel/issues/10681 Test Plan: bazel test //... works again on Bazel 2.2+ X-Origin-Diff: phab/D436 GitOrigin-RevId: d5700cbaa59fefd791f5c9902195f0294a0e6f07
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.