| commit | eff7217f788aae2af6b86dbb91defa3171eb88b8 | [log] [tgz] |
|---|---|---|
| author | Leopold Schabel <leo@nexantic.com> | Sat Jan 04 15:07:52 2020 +0100 |
| committer | Leopold Schabel <leo@nexantic.com> | Sat Jan 04 15:07:52 2020 +0100 |
| tree | c092558c9d6cc64725c1a41ed6797736ad5552e2 | |
| parent | a4516f9887e43b774e49c22db93cdf289dc9cfb1 [diff] |
Synthesize fake GOPATH and remove bazel_copy_generated_for_ide.sh We can use rules_go to create a fake symlink farm GOPATH. This can be set as the GOPATH in IDEs that do not have native support for Bazel, and we can stop maintaining the bazel_copy_generated_for_ide.sh hack. The remaining issue is that we still need Go tooling to manage our go.mod file that serves as the input to Gazelle, so we need to add replace directives to ensure that Go tools can resolve generated code. The proper fix for all this is the upcoming native Bazel support in Go: https://github.com/bazelbuild/rules_go/issues/512 Test Plan: Ran `bazel build :gopath`, and a wild `bazel-bin/gopath/src/git.monogon.dev/source/nexantic.git/core/generated/api/schema.pb.go` appeared. `scripts/symlink_generated_files.sh` created a valid symlink in core/generated and `go mod tidy` ran successfully (despite complaining about the symlink). Running `scripts/gazelle.sh` twice worked. X-Origin-Diff: phab/D305 GitOrigin-RevId: 0d456bc57d4a2d72e30865ffef777d2f5be5c407
This is the monorepo storing all of nexantic's internal projects and libraries.
We assume a Fedora 30 or 31 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.