| commit | f369cfa3ab4ad5ba882fa66f2fd1c3df8e5b4495 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Fri May 22 18:36:42 2020 +0200 |
| committer | Serge Bazanski <serge@nexantic.com> | Fri May 22 18:36:42 2020 +0200 |
| tree | 623bb7e085852f87e9ad6618408dc4b3171f7b29 | |
| parent | df12522ed48dbac7edbae32be01a09770b01d0f7 [diff] |
fietsje: implement This introduces Fietsje, a little Go dependency manager. For more information, see third_party/go/fietsje/README.md. We also bump some dependencies while we're at it, notably, sqliboiler now uses Go modules. If we weren't to do that, we'd have to add more heuristics to Fietsje to handle the old version correctly. Test Plan: fietsje is untested - I'll add some tests to it. Everything else is just regenerating basically the same repositories.bzl file, but with some bumped dependencies. X-Origin-Diff: phab/D535 GitOrigin-RevId: 4fc919e1bd386bc3f3c1c53e672b1e3b9da17dfc
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.