bringing back the lost per-project cmake executable setting
Morten Volden
mvolden2 at gmail.com
Sat Sep 16 11:12:28 UTC 2017
Hey Rene.
You are aware that some work has been done to that effect in the master
branch - right?
i.e. commit 4ee64bb2cf885d33ef914f7bda55a584722e0536
Kind Regards
Morten
2017-09-15 13:28 GMT+04:00 René J.V. Bertin <rjvbertin at gmail.com>:
> [Attn Aleix]
>
> In #b9a74648, Aleix thought to improve the cmake executable settings by
> making the setting kdevelop-wide. It's a real pity this didn't go through a
> patch review as I'd have a few words to say about it...
>
> Now if memory serves me well from the time I implemented the per-project
> CMake configuration settings, there was already a global setting for CMake.
> Maybe not of the binary, but if I made that setting per-project it wasn't
> just lazyness but also because I actually see justification for being able
> to specify this at a project level. I often have sessions where one project
> may use a bare-bones cmake, and another project a cmake wrapper or simply a
> cmake from another prefix that has different built-in search paths.
>
> I agree that having the possibility to configure a default value for this
> parameter (that overrides the hardcoded default) can be useful. It could be
> even more useful to make that a session-level parameter as already
> suggested in the commit message. But I'd *really* like to bring back
> project-level override. The UI is still there, and that particular UI is
> normally hidden so it's not like this will add additional clutter.
>
> I'll be looking into this but being new to the 5.2 branch and reorganised
> code structure (which probably makes it impossible to revert the commit) I
> wouldn't a little bit of a helping hand. ("you broke it, you fix it", eh
> ;))
>
> Thanks,
> R.
>
--
Regards / Med venlig hilsen
Morten Danielsen Volden
Software Developer
M.Sc. EE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20170916/ba31dfc0/attachment-0001.html>
More information about the KDevelop-devel
mailing list