Repository navigation
Conversation
…d OCCT detection, rebuild only when src/cpp changes) On a Windows machine without Visual Studio, scikit-build-core left the generator to CMake's default (NMake), the build failed with "'nmake' -? failed", and every contributor had to hand-set CMAKE_GENERATOR / CC / CXX / CMAKE_ARGS. uv also rebuilt the editable install on any pyproject.toml change (a version bump), which is how the failure showed up after the 2.2.9 release. - tools/build_backend/scad_build.py: a PEP 517 backend wrapping scikit-build-core. On Windows it uses Ninja + the gcc on PATH when Visual Studio is absent, finds OCCT (SCAD_OCCT_PREFIX, C:/occt, a per-user cache, or builds it once with tools/build_occt.py) and limits jobs by RAM (g++ ran out of memory under ninja's default). Anything the user or CI sets wins. - [tool.uv] cache-keys: rebuild only when src/cpp changes. Build tooling only: nothing in the published package changes, so no version bump. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This branch has not been deployed
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.
Problem
uv run/uv syncon Windows failed after the 2.2.9 release bump: uv rebuilds the editable install whenpyproject.tomlchanges, and without Visual Studio CMake defaulted to NMake ('nmake' -? failed). Contributors had to hand-setCMAKE_GENERATOR,CC,CXX,CMAKE_ARGS.Change
tools/build_backend/scad_build.py: PEP 517 backend wrapping scikit-build-core. On Windows: Ninja + gcc on PATH when VS is absent, OCCT located (SCAD_OCCT_PREFIX,C:/occt, per-user cache, else built once withtools/build_occt.py), job count limited by RAM. User/CI-set variables win; Linux/macOS untouched.[tool.uv] cache-keys: rebuild only whensrc/cppchanges, not on a version bump.Build tooling only, the published package is unchanged, so no release.
Tested
Windows 11, no VS, no env vars: a bare
uv runbuilds with Ninja + gcc and imports. The OCCT auto-build path (no OCCT present) and the cibuildwheel/sdist path are only covered by this PR's CI.🤖 Generated with Claude Code