| commit | 5e0bd2d43ab72cf4091e7689d02f95e07b1c1010 | [log] [tgz] |
|---|---|---|
| author | Hendrik Hofstadt <hendrik@nexantic.com> | Mon Feb 10 19:46:41 2020 +0100 |
| committer | Hendrik Hofstadt <hendrik@nexantic.com> | Mon Feb 10 19:46:41 2020 +0100 |
| tree | 24920f9a9a322b58fe79258a735af3a460dd08f1 | |
| parent | 7a1b10c4eb2a01084298537fae46f60ecf97cb6c [diff] |
Resolve embedded Go dependencies in IDEA
The bazel plugin aspects don't resolve embedded go libraries' source files.
```
go_proto_library(
name = "api_go_proto",
compilers = ["@io_bazel_rules_go//proto:go_grpc"],
importpath = "git.monogon.dev/source/nexantic.git/core/generated/api",
proto = ":api_proto",
visibility = ["//visibility:public"],
deps = ["//core/api/common:go_default_library"],
)
go_library(
name = "go_default_library",
embed = [":api_go_proto"],
importpath = "git.monogon.dev/source/nexantic.git/core/generated/api",
visibility = ["//visibility:public"],
)
```
In this case the IDEA plugin would load only the proto library since it exposes more source files. The plugin will always load the rule with the most exposed source files.
This means that if we add additional source files to the go rule but still less than the proto files, they will be dropped even though we have the embedding that should theoretically merge them.
This revision merges embedded and source files so we can add custom go code to schema packages.
Test Plan: patched and resynced
X-Origin-Diff: phab/D394
GitOrigin-RevId: 37639045a920b6d52e2e41119e5e06957b309f51
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.