Version:           4.2.3 (using KDE 4.7.0) 
OS:                Linux

For various reasons i can't use any of the supported build systems in kdevelop. As a result i have to make use of custom include paths by adding each include path to .kdev_include_paths in the project root. Unfortunately paths listed in that file only seem to work if they are absolute. This works fine until the project is worked on by another developer. They would have to create or generate the file tailored to their project path.

It would be nice if relative paths in the file (or perhaps with some prefix like "PROJECT_RELATIVE:" in the same vain as "RESOLVE:") could be treated as project relative so the file would work equally well for multiple people.

Reproducible: Didn't try

Steps to Reproduce:
1. Create a custom project (any build system where kdevelop doesn't know where the include files are).

2. Create a header file "foo/bar.hpp" in some include directory in the project.

3. Create an implementation file and enter "#include <foo/bar.hpp>"

4. The include line is underlined in red because kdevelop doesn't understand where include files live.

5. Hover over the include line and fix it using the custom include dialog.

Actual Results:  
If you enter an absolute path it can find the include file but when you transport the project directory to another computer (or even another directory) then it fails.

If you enter a relative path then kdevelop fails to find the file.

Expected Results:  
Relative paths should be resolved relative to the project root and the file is portable.