Skip to content

fix(install): reconfigure Packmol when the shared build cache comes from another checkout - #10

Merged
EricBoittier merged 1 commit into
mainfrom
fix/packmol-stale-build-cache
Nov 18, 2026
Merged

EricBoittier merged 1 commit into
mainfrom
fix/packmol-stale-build-cache

Conversation

@EricBoittier

Copy link
Copy Markdown
Owner

Summary

Found by the fresh-clone install check: scripts/rebuild_packmol.sh builds in $HOME/.cache/karml-packmol-build/<platform>, shared by all checkouts; CMake aborts with "does not match the source ... used to generate cache" when that cache came from another clone, which made make install-native fail after the CHARMM library had built. The script now drops only the stale configure state (CMakeCache.txt, CMakeFiles).

Tests

New tests/unit/test_rebuild_packmol_stale_cache.py (stub cmake/gfortran, mismatched cache): 1 passed. Real-world proof: fresh-clone check re-run, see PR comments.

🤖 Generated with Claude Code

…rom another checkout

make install-native failed with 'does not match the source ... used to generate cache' on a machine that had built another clone before.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@EricBoittier
EricBoittier merged commit e1649f9 into main Nov 18, 2026
9 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant