At a quick glance, here are a few missing features (one of which is a bit of a design bug): - there is no setting for the configuration environment as provided by the other project manager plugins - idem, the install prefix isn't separated out of the other options but hidden "somewhere in there" - there is no easy way to select compilers. The CMake plugin doesn't provide one either, but then it also doesn't provide a settings page called "Compiler" where you'd expect to be able to make this kind of choice. - project build options aren't saved in the .kdev4/foo.kdev4 settings file. The latter is a design error IMHO. Project options should (also) be saved in the project definition, so that you can easily perform a full clean build by trashing and recreating the build directory. I am aware that the CMake plugin also doesn't allow this, but again, it has many less configuration options built in: start a new project and you will have to specify any non-default settings via the cmake "extra arguments" (which will be stored in the .kdev4 file).
1. Setting > Configure KDevelop > Environment 2. When importing, opening or creating project you are asked about install prefix, you can then select desired environment for launcher 3. On linux One probably needs to change CC and CXX variables 4. I see KDevelop as IDE which is built around CMake. CMake takes care of most config options, when you want to change something change it in your buildsystem. I agree, it is sad that the project options are stored somewhere else. But again, when you want to change something or make your build better, you should change your build system. In general your program should build without IDE just by running build system (cmake, make, qmake, meson...). So things specialy set in kdevelop and not in build system would become major headache for many.
(In reply to Juraj from comment #1) > But again, when you want to change something or make your build better, you Again? > should change your build system. That's only an option with your own software, not with projects you participate in. > In general your program should build without IDE just by running build > system (cmake, make, qmake, meson...). Yes. > So things specialy set in kdevelop > and not in build system would become major headache for many. No, if so the implementation is wrong. If meson expects its settings in a file in the build directory (cf. CMakeCache.txt) then the file should be there. However, I notice that all the options you select in the settings UI are passed as commandline arguments when meson is run in a new build directory. So you *can* set all these parameters that way. In other words, it is possible to store all options set via KDevelop's settings dialog in the .kdev4 file, and use them when meson is invoked (always or when required). Basically it means you'd extend the "extra arguments" string with settings stored under a different key (or keys). Note that the CMake and QMake plugin already do this: install prefix and build type are set via widgets, and the settings are added to the "extra arguments" string. All this to achieve the possibility to define a more or less complex meson set-up in a KDevelop project, and reapply it when the build directory doesn't exist (you could distribute the .kdev4 files, for instance, like you can with an MSVC or Xcode project).