Plaintext format for custom include paths

[Milian Wolff]

On Tuesday 09 September 2014 20:52:52 Piotr Dziwinski 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.
> 
> So I'm wondering if there is a chance to restore previous behaviour or
> change the format to be more plaintext-like?

Hm that is a use-case I have not encountered so far. Do you really have to do 
this so often? Can you not set the include paths once in the project settings 
and be done with it?

For the future though I agree that we should do something about this. Maybe we 
could even extend the include path manager to optionally execute an external 
script to read include paths or something like that.

Bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de