Better IDE integration

Author: Evert

CMakeLists.txt

@@ -17,12 +17,6 @@ setup_compiler_launcher_if_available()
 # ────────────────────────────────────────────
 # Create compile_commands.json for IntelliSense and clang-tidy
 set(CMAKE_EXPORT_COMPILE_COMMANDS ON)
-# If we're not building through scikit-build-core then we have to set a different dest dir
-include(GNUInstallDirs)
-set(_DUCKDB_PY_INSTALL_DIR "${SKBUILD_PLATLIB_DIR}")
-if(NOT _DUCKDB_PY_INSTALL_DIR)
-  set(_DUCKDB_PY_INSTALL_DIR "${CMAKE_INSTALL_LIBDIR}")
-endif()
 
 # ────────────────────────────────────────────
 # Policy hygiene
@@ -87,4 +81,16 @@ target_link_libraries(_duckdb PRIVATE _duckdb_dependencies)
 # ────────────────────────────────────────────
 # Put the object file in the correct place
 # ────────────────────────────────────────────
+
+# If we're not building through scikit-build-core then we have to set a different dest dir
+include(GNUInstallDirs)
+if(DEFINED SKBUILD_PLATLIB_DIR)
+  set(_DUCKDB_PY_INSTALL_DIR "${SKBUILD_PLATLIB_DIR}")
+elseif(DEFINED Python_SITEARCH)
+  set(_DUCKDB_PY_INSTALL_DIR "${Python_SITEARCH}")
+else()
+  message(WARNING "Could not determine Python install dir. Falling back to CMAKE_INSTALL_LIBDIR.")
+  set(_DUCKDB_PY_INSTALL_DIR "${CMAKE_INSTALL_LIBDIR}")
+endif()
+
 install(TARGETS _duckdb LIBRARY DESTINATION "${_DUCKDB_PY_INSTALL_DIR}")

README.md

@@ -65,19 +65,6 @@ git config --local core.hooksPath .githooks/
 ```
 
 
-### Building wheels and sdists
-
-  To build a wheel and sdist for your system and the default Python version:
-```bash
-uv build
-````
-
-  To build a wheel for a different Python version:
-```bash
-# E.g. for Python 3.9
-uv build -p 3.9
-```
-
 ### Editable installs (general)
 
   It's good to be aware of the following when creating an editable install:
@@ -93,7 +80,7 @@ uv build -p 3.9
 # install all dev dependencies without building the project (needed once)
 uv sync -p 3.9 --no-install-project
 # build and install without build isolation
-uv sync  --no-build-isolation
+uv sync --no-build-isolation
 ```
 
 ### Editable installs (IDEs)
@@ -103,6 +90,28 @@ uv sync  --no-build-isolation
   compilation and editable rebuilds. This will skip scikit-build-core's build backend and all of uv's dependency 
   management, so for "real" builds you better revert to the CLI. However, this should work fine for coding and debugging.
 
+
+### Cleaning
+
+```shell
+uv cache clean
+rm -rf build .venv uv.lock
+```
+
+
+### Building wheels and sdists
+
+To build a wheel and sdist for your system and the default Python version:
+```bash
+uv build
+````
+
+To build a wheel for a different Python version:
+```bash
+# E.g. for Python 3.9
+uv build -p 3.9
+```
+
 ### Running tests
 
   Run all pytests:

pyproject.toml

@@ -112,6 +112,7 @@ if.state = "editable"
 if.env.COVERAGE = false
 build-dir = "build/debug/"
 editable.rebuild = true
+editable.mode = "redirect"
 cmake.build-type = "Debug"
 
 # Separate override because we have to append to cmake.define with `inherit` in order not to overwrite other defines.