docs: document the build variants pixi sets automatically#6534
Open
hunger wants to merge 1 commit into
Open
Conversation
Pixi fills in some build variants for you rather than requiring them in [workspace.build-variants]: target_platform, and c_stdlib/c_stdlib_version derived from the target platform's system requirements when building against conda-forge. Only the compiler defaults were documented before. Add a "Variants Pixi Sets for You" section to the build variants tutorial covering the derivation, its conda-forge gating, the bare-subdir defaults, and the Windows/musl/CUDA limitations, and cross-reference it from the manifest reference.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pixi fills in some build variants for you rather than requiring them in [workspace.build-variants]: target_platform, and c_stdlib/c_stdlib_version derived from the target platform's system requirements when building against conda-forge. Only the compiler defaults were documented before.
Add a "Variants Pixi Sets for You" section to the build variants tutorial covering the derivation, its conda-forge gating, the bare-subdir defaults, and the Windows/musl/CUDA limitations, and cross-reference it from the manifest reference.
How Has This Been Tested?
By reading it :-)
AI Disclosure
Tools: Claude
Checklist:
schema/model.py.