summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKlaus T. Aehlig <aehlig@linta.de>2024-02-02 11:00:38 +0100
committerKlaus T. Aehlig <aehlig@linta.de>2024-02-02 20:27:24 +0100
commitd71277e0a0b6ad60b6ecce4382b7f7f3e35c3282 (patch)
treed1852f2a6b1baa853e00dcc6744de8ea309619c4
parentb9d3b2ef9e79878c422433c0289a2613fee11001 (diff)
downloadjustbuild-d71277e0a0b6ad60b6ecce4382b7f7f3e35c3282.tar.gz
Fix export of remote API
As we patch that API, it also can implicitly depend on the toolchain (and hence its config), if we use a compiled implementation of patch. Making the TOOLCHAIN_CONFIG a flexible part of the config allow to, again, build static binaries as usual.
-rw-r--r--etc/import/TARGETS.bazel_remote_apis3
1 files changed, 2 insertions, 1 deletions
diff --git a/etc/import/TARGETS.bazel_remote_apis b/etc/import/TARGETS.bazel_remote_apis
index a74b9ef0..efc3ddd0 100644
--- a/etc/import/TARGETS.bazel_remote_apis
+++ b/etc/import/TARGETS.bazel_remote_apis
@@ -31,6 +31,7 @@
, "The Remote Execution API is an API that, at its most general, allows clients"
, "to request execution of binaries on a remote system."
]
- , "flexible_config": ["ARCH", "ENV", "HOST_ARCH", "PATCH"]
+ , "flexible_config":
+ ["ARCH", "ENV", "HOST_ARCH", "PATCH", "TOOLCHAIN_CONFIG"]
}
}