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
Copy file name to clipboardExpand all lines: docs/index.md
+65Lines changed: 65 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,6 +47,71 @@ Check out our [tutorial series](https://pixi.sh/latest/build/getting_started/) t
47
47
48
48
Learn how pixi-build integrates with conda-forge's compiler infrastructure to provide cross-platform, ABI-compatible builds. Covers compiler configuration, platform-specific behavior, and available compiler options for supported backends.
49
49
50
+
## 🔧 Troubleshooting
51
+
52
+
### Rebuilding Generated Recipes
53
+
54
+
When you build a package using `pixi build`, the build backends generate a complete rattler-build recipe that is stored in your project's build directory. This can be useful for debugging build issues or understanding exactly how your package is being built.
55
+
56
+
### Recipe Locations
57
+
58
+
The build backends generate recipes in two locations:
* Debug build failures with direct access to `rattler-build`
110
+
* Understand how the build backend translated your project model (`pixi.toml`)
111
+
112
+
!!! tip
113
+
The `<variant_hash>` ensures that each unique combination of build variants gets its own recipe directory, making it easy to compare different build configurations.
114
+
50
115
## 🔗 Useful Links
51
116
52
117
-[GitHub](https://github.com/prefix-dev/pixi): Pixi source code, feel free to leave a star!
0 commit comments