tags:

views:

274

answers:

2

Hi,

I installed cedet successfully today and got most of it working; thanks to Alex Ott's Gentle Introduction to Cedet.

However i am having a problem

When I give the exact path relative to the current file i am working on then auto-completion is working fine.

#include "../../opensource/inc/lldp_port.h"
void test_func()
{
    lldp_port port;
    port.blah //here auto-completion worked fine
}

However i cannot specify the full path all the time( we have eclipse at office and it generates makefiles for us )

#include "lldp_port.h"
void test_func()
{
    lldp_port port;
    port. //here auto-completion does not work :(
}

What should i do to solve this?

+3  A: 

One of the arguments to CEDET's project setup function is include-path. There's an example here:

(ede-cpp-root-project "NAME" :file "FILENAME"
     :include-path '( "/include" "../include" "/c/include" )
     :system-include-path '( "/usr/include/c++/3.2.2/" )
     :spp-table '( ("MOOSE" . "")
                   ("CONST" . "const") )
     :spp-files '( "include/config.h" )
     ) 
Michael Mrozek
just correction: system-include-path is usually detected automatically via semantic-gcc, but it could be used to specify path to other libraries, not included into project
Alex Ott
A: 

The project I am working in is huge. It has many many many directories. It would be great if there is an option in cedet to work more like how omnicomplete works in vim - parse the TAGS file and give me the result. Anybody knows how to do that?

trybeingarun
You are much more likely to get an answer to this question if you post it as a new question.
High Performance Mark
For this it's better to use GNU Global - it works better as standard tags. Although CEDET has support for both - look to semanticdb-global and semanticdb-ectag packages in CEDET. These options are described in CEDET documentation and my article
Alex Ott