Plaintext format for custom include paths

Aleksey Midenkov midenok at
Fri Sep 19 13:47:10 BST 2014

On Tue, Sep 9, 2014 at 10:52 PM, Piotr Dziwinski <piotrdz at> wrote:
> Hello,
> I have a question regarding the new mechanism for specifying custom include
> paths in KDevelop 4.7. I see that the new plugin "custom-definesandincludes"
> has changed the previous mechanism of listing include paths in
> ".kdev_include_paths" files to settings kept in project's settings file.
> This is unfortunate for me since I use a set of scripts for automatically
> managing the ".kdev_include_paths" file for a large project. The new
> settings file is saved using QDataStream and not in simple plaintext as
> before and I cannot easily read or write to it using bash scripts anymore.

I hope, project files are still in plain text? I generate project
files from m4 macros. Does binary format do any good here? I think
it's inconvenient. The whole difference between Windows-style (binary
registry) and Unix-style (a bunch of plain text files) means a lot to

More information about the KDevelop mailing list