From 201726cda527340bd3becf84547f3dc36f5098a2 Mon Sep 17 00:00:00 2001 From: FishAlchemist <48265002+FishAlchemist@users.noreply.github.com> Date: Fri, 10 Jan 2025 01:41:04 +0800 Subject: [PATCH] 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. https://github.com/astral-sh/uv/pull/10261/commits/9821d58d35dce6bbafe4bdadd9031afba0f787a5 ![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 --- docs/concepts/projects/config.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/concepts/projects/config.md b/docs/concepts/projects/config.md index 3fa7c0888..6e1f84632 100644 --- a/docs/concepts/projects/config.md +++ b/docs/concepts/projects/config.md @@ -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.