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

![image](https://github.com/user-attachments/assets/3c07ac15-a562-40e2-9289-204c0975261f)

---------

Signed-off-by: FishAlchemist <48265002+FishAlchemist@users.noreply.github.com>
Co-authored-by: Zanie Blue <contact@zanie.dev>
This commit is contained in:
FishAlchemist 2025-01-10 01:41:04 +08:00 committed by GitHub
parent 19589e0614
commit 201726cda5
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -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.