Skip to content

docs: Add note on conda requirements #63

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
matthewfeickert merged 1 commit into from
Jul 14, 2026
Merged

docs: Add note on conda requirements #63

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions content/other-tools/02_pixi_build.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,16 @@ To learn the sections and functionalities by example rather than by inspection o

## Basic Packaging

:::{note} Build, Host, and Run conda requirements

When building conda packages, recipes have the concept of `build`, `host`, and `run` requirements.

* `build`: Tools that are used to perform the actual build (e.g. `cmake`, `ninja`)
* `host`: Packages that supply development requirements for the package you're building, like headers or shared libraries that are linked against (e.g. `boost-devel`)
* `run`: The requirements of your package to actually run (e.g. your `pyproject.toml` `dependencies`)

:::

### Configuring the Pixi manifest

Take the example Python package directory tree from [Making a basic package](https://scikit-build.org/SIMPLE-Py/package/) as a starting foundation.
Expand Down
15 changes: 15 additions & 0 deletions slides/5_02_pixi_build.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,21 @@ _class: lead

---

# Build, host, and run requirements

When building conda packages, recipes have the concept of `build`,
`host`, and `run` requirements:

- `build`: Tools that are used to perform the actual build
(e.g. `cmake`, `ninja`)
- `host`: Packages that supply development requirements for the
package you're building, like headers or shared libraries that are
linked against (e.g. `boost-devel`)
- `run`: The requirements of your package to actually run
(e.g. your `pyproject.toml` `dependencies`)

---

# Basic packaging: starting point

Take the `rescale` package from _Making a basic package_ and create a
Expand Down