| commit | f8323f1010f4d1714570197f438888d081056846 | [log] [tgz] |
|---|---|---|
| author | Leopold Schabel <leo@nexantic.com> | Tue Jan 07 23:26:34 2020 +0100 |
| committer | Leopold Schabel <leo@nexantic.com> | Tue Jan 07 23:26:34 2020 +0100 |
| tree | 58c3328cd2e1a576d0aa29ccebac6dd7b6a3077a | |
| parent | 83dc285944ad65d429bb2641a7348366e7028c40 [diff] |
Remove synthetic GOPATH and symlinks As it turns out, `go mod tidy` complains about missing modules but still properly generates go.mod, so it appears that we do not need a GOPATH or symlinks except for non-IntelliJ IDE support. We should standardize on IntelliJ and just get rid of this workaround. Hendrik had trouble rebasing the shield revisions (that have a lot of generated code) and it's likely a lot of work to maintain this hack in the future. See D305, D309 Test Plan: Ran `scripts/gazelle.sh` after deleting all symlinks and tested that `go mod tidy` properly restored the go.mod file after modifying it manually. X-Origin-Diff: phab/D311 GitOrigin-RevId: fe4bc491fca6fa072cff047185d7c18305564ea4
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.