Re: [CEDET-devel] ede-cpp-root-project behavior

[Eric M. L. <er...@si...>]

On 03/24/2011 12:21 AM, MK wrote:
> Hello,
>
> I have just started using CEDET so it is likely I am doing something
> wrong, but :
>
> The common understanding seems to be that if I use
> ede-cpp-root-project and set :file to a file in the top level
> directory, then this ede project will recursively scan all subdirs and
> make all the files in all the subdirs available to semantic for
> intellisense. (As per maillist archives etc)

ede-cpp-root doesn't scan any files.  It just marks the root of a 
project.  You would still need to define include paths and such to get 
additional Semantic features working.

> Is this really the case?
>
> If I do that then M-x ede-find-file can only find files in the top
> level directory. Also, intellisense functions like M-x
> semantic-ia-fast-jump etc only seem to find things in the top level
> directory.

Right.  If you want ede-find-file to work, you can get a scanning tool 
like GNU Global, and perform its setup, and then that will work.  For 
intellisense, that needs a good set of include paths setup, at which 
point it will start looking up symbols via header files.

> In real life projects, it is often the case that the application you
> are working on has many different libraries and these libraries will
> not always be subdirectories under the application directories. How
> can I represent such a structure in ede to make it available to
> semantic?

This is where include paths are important.  ede-cpp-root lets you 
specify where in the project to find local headers, and where outside 
the project to look for even more headers.

It assumes a simple simple program, and nothing very complex.  complex 
projects would need some custom coding to get them working right.

Eric