You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
5. This will allow pixi to install desired backends from the `pixi-build-backends` channel, and any requirements from `conda-forge`. Backends are installed into isolated environments, and will be shared across pixi projects.
16
+
17
+
### Overriding the Build Backend
18
+
Sometimes you want to override the build backend that is used by pixi. Meaning overriding the backend that is specified in the [`[build-system]`](../reference/pixi_manifest.md#the-build-system). We currently have two environment variables that allow for this:
19
+
20
+
1.`PIXI_BUILD_BACKEND_OVERRIDE`: This environment variable allows for overriding of one or multiple backends. Use `{name}={path}` to specify a backend name mapped to a path and `,` to separate multiple backends.
21
+
For example: `pixi-build-cmake=/path/to/bin,pixi-build-python` will:
22
+
1. override the `pixi-build-cmake` backend with the executable located at `/path/to/bin`
23
+
2. and will use the `pixi-build-python` backend from the `PATH`.
24
+
2.`PIXI_BUILD_BACKEND_OVERRIDE_ALL`: If this environment variable is set to *some* value e.g `1` or `true`, it will not install any backends in isolation and will assume that all backends are overridden and available in the `PATH`. This is useful for development purposes. e.g `PIXI_BUILD_BACKEND_OVERRIDE_ALL=1 pixi install`
@@ -840,8 +835,7 @@ For Python packages, these are the most common dependency types.
840
835
For compiled languages, these are less common and would basically be dependencies that you do not need when compiling the package but are needed when running it.
0 commit comments