*: replace nxt -> monogon
These are hopefully the last leftovers from the nxt monorepo.
This change breaks existing build containers and IntelliJ setups, and
unfortunately thrashes developer workstation Bazel caches.
Running `scripts/bin/destroy_container.sh &&
scripts/bin/create_container.sh` and then following the IntelliJ setup
guide in //README.md should be enough to fix everything.
Did that locally and was able to set up a fully working IntelliJ
IDE against this change.
Change-Id: I090f4e4f2ea03998569a4ea3d1aa4cd4ec570f8a
Reviewed-on: https://review.monogon.dev/c/monogon/+/61
Reviewed-by: Leopold Schabel <leo@nexantic.com>
diff --git a/README.md b/README.md
index 6fb8def..6393910 100644
--- a/README.md
+++ b/README.md
@@ -29,10 +29,10 @@
- Install Google's [Bazel plugin](https://plugins.jetbrains.com/plugin/8609-bazel) in IntelliJ. On IntelliJ 2020.3 or later,
you need to install a [beta release](https://github.com/bazelbuild/intellij/issues/2102#issuecomment-801242977) of the plugin.
-- Add the absolute path to your `~/.cache/bazel-nxt` folder to your `idea64.vmoptions` (Help → Edit Custom VM Options)
+- Add the absolute path to your `~/.cache/bazel-monogon` folder to your `idea64.vmoptions` (Help → Edit Custom VM Options)
and restart IntelliJ:
- `-Dbazel.bep.path=/home/leopold/.cache/bazel-nxt`
+ `-Dbazel.bep.path=/home/leopold/.cache/bazel-monogon`
- 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.