https://bugs.kde.org/show_bug.cgi?id=384726
Bug ID: 384726
Summary: per-project cmake setting ignored
Product: kdevelop
Version: unspecified
Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: Build tools: CMake
Assignee: kdevelop-bugs-n...@kde.org
Reporter: rjvber...@gmail.com
Target Milestone: ---
KDevelop 5.1.40 (5.1.2.15137) has a blocker bug for me:
1. open a project with a custom cmake path configured (say
`/opt/local/bin/cmake2port`, a wrapper around cmake)
2. open the project configuration dialog, check the advanced settings
3. The field that should show `/opt/local/bin/cmake2port` is empty; enter the
appropriate value
4. Accept the dialog.
KDevelop will now launch the default cmake executable and then reload the
project.
Go back to step 2 ...
This still worked in 5.1.2.5, the last commit in the 5.1.2 branch. I think I've
seen this issue mentioned but couldn't find a ticket, so here it is.
As far as I can tell, the custom cmake binary setting *is* stored in the
project settings file; after going back to the last working release it
reappeared in the project configuration dialog.
--
You are receiving this mail because:
You are watching all bug changes.
