diff options
| author | Marco Farrugia <afmarco@gmail.com> | 2020-09-23 22:56:41 -0400 |
|---|---|---|
| committer | Profpatsch <mail@profpatsch.de> | 2020-10-19 18:32:48 +0200 |
| commit | a360b05cb719c26260eb6d37762549f419dd98d5 (patch) | |
| tree | b19305412c44e39ea695a2e2db7c1895a302a680 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 67d2de5ffaa6766a71b077a331b1cad07b7e3a80 (diff) | |
bazel: Fix bazel query and provide a default java toolchain
These are fixes for problems I ran into with:
- `bazel test //example:cpp-test`
This needed `build --host_javabase='@local_jdk//:jdk'`
- `bazel query 'deps(//example:cpp-test)'`
This needed the same flags as `build`.
Is it contentious to (partially?) configure the default java toolchain? I don't see it as much different than providing the bazel server's java.
It would continue to be configurable/overridable by overriding the flags.
---
And a random notes from this escapade, but https://github.com/bazelbuild/bazel/blob/master/WORKSPACE#L144-L308 looks a little different from https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/tools/build-managers/bazel/bazel_3/src-deps.json so one of them is probably wrong :)
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions