If you use EDE to identify your project, and if you keep your cscope
database in the root of that project, then everything else is automatic.
If after doing the basic cscope setup (see the cedet.info manual) you type:
you will see the commands you can use to query cscope (like if a
directory has a database supporting it, version check, etc). You can
use those commands to test if things don't appear to work as you expect.
There is also a command to create the cscope database which may be handy.
On 07/29/2013 03:52 PM, Jai Dayal wrote:
> So if we want CEDET to use cscopes, we have to build the cscopes
> database for our project? That's reasonable. I suppose there's a way to
> tell CEDET which cscopes database to use. Can you have multiple loaded
> at the same time? Does this work with the EDE stuff?
> On Mon, Jul 29, 2013 at 4:30 AM, Eric M. Ludlam <eric@...
> <mailto:eric@...>> wrote:
> This is a nice tutorial that Alex Ott put together on CEDET:
> The CEDET tools can stand alone, but can also use things like cscope or
> GNU Global to improve how it works, and you example is one of those
> The CEDET parser only parses the files you have opened at some point in
> the past, and if you have set things up (as per tutorial above) so it
> can find your header files (or equivalent for your language) it can also
> find tags in those headers. As such, it starts with a limited set.
> cscope and Global both parse your whole project first. CEDET can use
> the tags created by those tools as a fast way to get full-project symbol
> jumping working without waiting for Emacs to parse all your files.
> If you are ONLY looking for jump-to-tag type functionality, etags (which
> comes with Emacs) can be sufficient for most people, particularly in a
> language like C. CEDET can provide a lot more above and beyond that
> On 07/26/2013 09:23 AM, Matt Funk wrote:
> > Hi Eric,
> > 1) so the equivalent to the code browsing capability that cscope
> > provides (via a tag-based system) is done by semantic (a true source
> > code parser) and exposed via senator for source code navigation
> (such as
> > finding the declaration)? Did i get that right? I read the
> > documentation, but i was still a little hazy exactly on how
> things work.
> > I am a little slow sometimes.
> > 2) For starters, say i don't have cscope integrated, how would i go
> > about jumping to a function declaration? I tried to get to a function
> > declaration via semantic-ia-fast-jump <functionname> but that did not
> > work. It says: could not find <functionname>. So somewhere i am
> > something ...
> > 3) Is there a simple howto (possibly with some open source
> project) that
> > guides the new cedet user through using the basic features (such as:
> > find declaration, find references) since i don't want to bug the list
> > all the time ...
> > thanks,
> > matt
> > On Fri, Jul 26, 2013 at 1:00 AM, Eric M. Ludlam
> <eric@... <mailto:eric@...>
> > <mailto:eric@... <mailto:eric@...>>> wrote:
> > On 07/25/2013 11:40 AM, Matt Funk wrote:
> > Hi,
> > i am new to cedet and have been using eclipse to do
> > I am
> > looking to have emacs be my main "ide".
> > My problem is the following:
> > I am working on a large project and i am trying to look
> up the
> > declaration of a function that i want to look at.
> > So i do C-c sd <functionname>
> > which will return a huge list of references. I would have
> > expected for
> > it to list a single reference that i can choose to open.
> > does
> > this when i say open declaration.
> > I am unfamiliar with a key sequence "C-c sd". What does that do?
> > It sounds like it requests the list of places where
> functionname is
> > used, as opposed to declared. If I recall my basic cscope, there
> > are several types of questions to ask, such as where something is
> > declared vs used.
> > If you have integrated cscope with CEDET, you would use something
> > like "semantic-ia-fast-jump", or one of the other jump calls, and
> > one of the "semantic-symref-*" functions to get the references.
> > Eric
> > See everything from the browser to the database with AppDynamics
> > Get end-to-end visibility with application monitoring from
> > Isolate bottlenecks and diagnose root cause in seconds.
> > Start your free trial of AppDynamics Pro today!
> > _______________________________________________
> > cedet-semantic mailing list
> > cedet-semantic@...
> > https://lists.sourceforge.net/lists/listinfo/cedet-semantic
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> cedet-semantic mailing list