Skip to content

pixi logo

Pixi Build Backends#

Backend Implementations for Building Pixi Projects from Source

Pixi Build Backends is a collection of specialized build backend implementations designed to facilitate building Pixi packages directly from their source code. These backends enable seamless integration with the Pixi ecosystem, supporting multiple programming languages and build systems while maintaining the conda ecosystem's cross-platform compatibility.

🚀 What Are Build Backends?#

Build backends are executables that follow a specific protocol to decouple the building of conda packages from Pixi itself. This architecture allows for:

  • Language-specific optimization: Each backend is tailored for specific programming languages and build tools
  • Modular design: Backends can be developed, updated, and distributed independently
  • Extensibility: New backends can be added without modifying Pixi core
  • Standardization: All backends follow the same protocol and manifest specifications

📦 Available Backends#

The repository currently provides four specialized build backends:

Backend Use Case
pixi-build-cmake Projects using CMake
pixi-build-python Building Python packages
pixi-build-rattler-build Direct recipe.yaml builds with full control
pixi-build-rust Cargo-based Rust applications and libraries

All backends are available through the prefix.dev/pixi-build-backends conda channel and work across multiple platforms (Linux, macOS, Windows).

🛠️ Getting Started#

Check out our tutorial series to learn how to use pixi build in practice.

  • GitHub: Pixi source code, feel free to leave a star!
  • Discord: Join our community and ask questions.
  • Prefix.dev: The company behind Pixi, building the future of package management.
  • conda-forge: Community-driven collection of recipes for the conda package manager.
  • Rattler: Everything conda but built in Rust. Backend of Pixi.
  • rattler-build: A blazing fast build system for conda packages.