https://bugs.kde.org/show_bug.cgi?id=412473
--- Comment #2 from RJVB <rjvber...@gmail.com> --- (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). -- You are receiving this mail because: You are watching all bug changes.
