Bug 258990

Summary: JJ: Allow setting per-configuration cmake options without a configured build directory
Product: [Applications] kdevelop Reporter: Alexander <ashaduri>
Component: Build tools: CMakeAssignee: kdevelop-bugs-null
Status: RESOLVED FIXED    
Severity: wishlist CC: gmary
Priority: NOR Keywords: junior-jobs
Version First Reported In: git master   
Target Milestone: 4.2.0   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Alexander 2010-12-06 10:44:02 UTC 
Version:           SVN (using KDE 4.5.3) 
OS:                Linux

I'm using KDevelop from git master (2010-12-03).

I have this issue with KDevelop's CMake configuration: Suppose I spent quite some time to find out the cmake variables needed to properly compile my project in Debug mode using clang. So I set all those variables there in the dialog, but if I delete the build directory (because, for example, it screws up the build), all my custom-set variables are gone.

So, I'd like to be able to specify per-configuration cmake variables that don't get erased along with the build directory. Maybe in a separate list, or a line that gets passed as an argument to cmake at configure stage (I would specify several -DCMAKE_VAR=something entries there). The last one is probably easier to implement.

Thanks

Reproducible: Always
Comment 1 Milian Wolff 2010-12-06 12:12:47 UTC 
adding history to the lineedit for custom cmake parameters in the initial "select build dir" dialog would be good
Comment 2 Ghislain MARY 2012-04-27 12:36:10 UTC 
I sumbitted a patch to add history for extra arguments in the build directory configuration dialog: https://git.reviewboard.kde.org/r/104755/
Comment 3 Milian Wolff 2012-04-30 13:52:25 UTC 
fixed by: https://git.reviewboard.kde.org/r/104755/