Relating upgrade to Kdevelop 4from Sabrina

Milian Wolff mail at
Sat Aug 27 00:11:43 UTC 2011

On Thursday 18 August 2011 23:32:38 Sabrina Friedman wrote:
> Hi list,
> I recently upgraded to kdevelop 4 after using kdevelop 3 for a long long
> time.
> I must say you guys have done a terrific job. Hats off.
> I would like to point out that I do experience certain difficulties
> with existing code.
> I have a large code base with code in different folders like
> My Code directory:
> file1.c
> file2.c
> file1.h
> file2.h
> Folder1-> file3.c file3.h
> Folder2-> file4.c file4.h
> So I import a project and add My code directory. All the files are
> added to the project but I am not able to understand how kdevelop's
> parser finds the declarations and definitions of all the functions and
> datatypes etc. It finds declarations for functions declared in the
> same file. Sometimes it does find declarations if they are in some
> other file in the same folder but does not find
> declarations/definitions if they are in files in different
> directories.

I don't quite get the problem: Declarations and definitions are found by 
parsing files. If you use stuff from fileX in fileY, you need a proper #include 
directive in fileY for fileX.

Depending on your project, this should work fine automagically, as we e.g. 
understand your CMake files and find the proper include paths from there.

If otoh you use some not-so-easy custom make files, this might file and you'll 
need to create a .kdev_include_paths file (or better yet, use the built-in UI 
to solve the "problem" for the not-found include path - just hover the 
problematic #include directive).

Milian Wolff
mail at
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <>

More information about the KDevelop-devel mailing list