Relating upgrade to Kdevelop 4

[Milian Wolff]

elison.niven at gmail.com, 10.08.2011:
> Aleix wrote :
> >We can't use ctags in KDevelop4, here the plan would be to use a buildtool
> >(cmake, makefile) that tells us what are the include directories and
> >defines or you can have the custom build system where you will tell
> >kdevelop specifically what are the include directories and so.
> 
> Hi,
> Can you help me with how to specify the include directories and
> defines to KDevelop. I am using my own Makefile for a C/C++ project.
> Right now I am using a variable in the Makefile to store the Include
> directories and pass it to the compiler options as -I.

just hover an include that kdev says it's not finding. it will offer you a way 
to define custom include paths. basically it's just putting a 
".kdev_include_paths" file into your source folder(s).

> I am not using cmake. Will using cmake help me here?

CMake would definitely help as it's much better integrated in KDevelop and 
makes your live easier in general. Anyhow, it's your choice on whether you 
want to use it or not. I'd say: try it out, it's worth it.

bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- 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: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20110810/151216b5/attachment.sig>