mirror of
https://github.com/astral-sh/uv.git
synced 2025-11-01 20:31:12 +00:00
docs: Clarify build system specific features usage. (#10261)
## Summary
Since there are occasional inquiries about how to configure UV for
build-system specific features, I want to raise awareness that users
should refer to the documentation of the build system they are using for
relevant settings.
## Test Plan
Run docs service in local.
9821d58d35

---------
Signed-off-by: FishAlchemist <48265002+FishAlchemist@users.noreply.github.com>
Co-authored-by: Zanie Blue <contact@zanie.dev>
This commit is contained in:
parent
19589e0614
commit
201726cda5
1 changed files with 12 additions and 0 deletions
|
|
@ -119,6 +119,18 @@ with the default build system.
|
|||
installable. Similarly, if you add a dependency on a local package or install it with `uv pip`,
|
||||
uv will always attempt to build and install it.
|
||||
|
||||
### Build system options
|
||||
|
||||
Build systems are used to power the following features:
|
||||
|
||||
- Including or excluding files from distributions
|
||||
- Editable install behavior
|
||||
- Dynamic project metadata
|
||||
- Compilation of native code
|
||||
- Vendoring shared libraries
|
||||
|
||||
To configure these features, refer to the documentation of your chosen build system.
|
||||
|
||||
## Project packaging
|
||||
|
||||
As discussed in [build systems](#build-systems), a Python project must be built to be installed.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue