cmake caches PYTHON_DEST after first run of cmake-gui
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 160
- Forks
- 113
- Avg merge
- 12d 15h
- Merged PRs (30d)
- 1
Description
If you run cmake-gui (or ccmake) first, and then change CMAKE_INSTALL_PREFIX, then it keeps PYTHON_DEST (and STIR_CONFIG or so) pointing to the original, i.e. /usr/local on Linux.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with cmake-gui or ccmake by configuring once, changing CMAKE_INSTALL_PREFIX, and configuring again. Trace where PYTHON_DEST and STIR_CONFIG are set, then verify that they follow the updated prefix rather than retaining /usr/local.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100