Thread: [cedet-semantic] semantic detabase for lots of intertwined projects
Brought to you by:
zappo
From: Jai D. <day...@gm...> - 2012-10-09 15:28:20
|
Hi all, Somewhat of a basic CEDET question here. I have a root folder called "mware", and within mware, there are several projects and codes which are related. for example, ATL, gen_thread, evpath.. etc. Some of them have dependencies (like evpath requires the previous two). How do I "build a database" in semantic, or something, that will have information for all of the associated projects, so that when I come across a struct or function, I can do semantic-ia-fast-jump and it will bring me to the appropriate definition. Maybe I have to do this via csopes? but it seems that cscopes just shows you where things are defined, whereas semantic will let you jump. Any ideas on how I can do this, preferably something wtih my .emacs file so I don't have to do it each time? Thanks so much! Jai |
From: Jai D. <day...@gm...> - 2012-10-10 14:05:29
|
Any advice? Thanks, Jai On Tue, Oct 9, 2012 at 11:27 AM, Jai Dayal <day...@gm...> wrote: > Hi all, > > > Somewhat of a basic CEDET question here. I have a root folder called > "mware", and within mware, there are several projects and codes which are > related. for example, ATL, gen_thread, evpath.. etc. Some of them have > dependencies (like evpath requires the previous two). > > How do I "build a database" in semantic, or something, that will have > information for all of the associated projects, so that when I come across > a struct or function, I can do > > semantic-ia-fast-jump > > and it will bring me to the appropriate definition. > > Maybe I have to do this via csopes? but it seems that cscopes just shows > you where things are defined, whereas semantic will let you jump. > > Any ideas on how I can do this, preferably something wtih my .emacs file > so I don't have to do it each time? > > Thanks so much! > Jai > |
From: Jai D. <day...@gm...> - 2012-10-11 00:46:21
|
Is everyone just ignoring me lol On Wed, Oct 10, 2012 at 10:04 AM, Jai Dayal <day...@gm...> wrote: > Any advice? > > Thanks, > > Jai > > > On Tue, Oct 9, 2012 at 11:27 AM, Jai Dayal <day...@gm...> wrote: > >> Hi all, >> >> >> Somewhat of a basic CEDET question here. I have a root folder called >> "mware", and within mware, there are several projects and codes which are >> related. for example, ATL, gen_thread, evpath.. etc. Some of them have >> dependencies (like evpath requires the previous two). >> >> How do I "build a database" in semantic, or something, that will have >> information for all of the associated projects, so that when I come across >> a struct or function, I can do >> >> semantic-ia-fast-jump >> >> and it will bring me to the appropriate definition. >> >> Maybe I have to do this via csopes? but it seems that cscopes just shows >> you where things are defined, whereas semantic will let you jump. >> >> Any ideas on how I can do this, preferably something wtih my .emacs file >> so I don't have to do it each time? >> >> Thanks so much! >> Jai >> > > |
From: David E. <de...@ra...> - 2012-10-11 21:19:35
|
Jai Dayal writes: > Is everyone just ignoring me lol Please note that we actually have other things to do besides CEDET. You know, job, kids, throwing pumpkins, that kind of stuff. The latter only Eric does, though. Anyway, EDE was already mentioned, and that's indeed the way to go. I'm guessing you're talking about a C/C++ project; the simplest way to set this up is to use ede-cpp-root-project, for example (ede-cpp-root-project "myproject" :file "~/mware/README.txt" :include-path '( "/someinclude" "/somewhere/core/include" "/whatever/api/include") :system-include-path '( "/usr/include/" "/usr/include/libxml2" "/usr/include/curl")) Note that the file you put in :file does not matter, it only has to exist in the root folder, and everything in :include-path is relative to this root. Please see the EDE documentation for further details (in the info documentation or online at http://www.randomsample.de/cedetdocs/ede/ede/ede_002dcpp_002droot.html ) -David |
From: Eric M. L. <eri...@gm...> - 2012-10-12 02:08:30
|
On 10/11/2012 05:19 PM, David Engster wrote: > Jai Dayal writes: >> Is everyone just ignoring me lol > > Please note that we actually have other things to do besides CEDET. You > know, job, kids, throwing pumpkins, that kind of stuff. The latter only > Eric does, though. > > Anyway, EDE was already mentioned, and that's indeed the way to go. I'm > guessing you're talking about a C/C++ project; the simplest way to set > this up is to use ede-cpp-root-project, for example > > (ede-cpp-root-project "myproject" :file "~/mware/README.txt" > :include-path '( "/someinclude" "/somewhere/core/include" > "/whatever/api/include") > :system-include-path '( "/usr/include/" > "/usr/include/libxml2" "/usr/include/curl")) > > Note that the file you put in :file does not matter, it only has to > exist in the root folder, and everything in :include-path is relative to > this root. Please see the EDE documentation for further details (in the > info documentation or online at > > http://www.randomsample.de/cedetdocs/ede/ede/ede_002dcpp_002droot.html > > ) I agree with David, particularly about the pumpkin throwing part. The one thing I would add is that if your primary use case is jumping around between symbols, and if you program typically in a functional setting, you should also try out the GNU Global integration under EDE and SemanticDB. The CEDET manual shows how to integrate it in these two places. This will allow you to jump around to files you haven't visited yet. Good Luck Eric |
From: <kon...@gm...> - 2012-10-11 07:48:55
|
Hi, Have you taken a look at EDE. I don't know what it does exactly but it seems to be the way to go when dealing with projects. Regards -- Samuel Jai Dayal <day...@gm...> writes: > Any advice? > > Thanks, > > Jai > > On Tue, Oct 9, 2012 at 11:27 AM, Jai Dayal <day...@gm...> wrote: > >> Hi all, >> >> >> Somewhat of a basic CEDET question here. I have a root folder called >> "mware", and within mware, there are several projects and codes which are >> related. for example, ATL, gen_thread, evpath.. etc. Some of them have >> dependencies (like evpath requires the previous two). >> >> How do I "build a database" in semantic, or something, that will have >> information for all of the associated projects, so that when I come across >> a struct or function, I can do >> >> semantic-ia-fast-jump >> >> and it will bring me to the appropriate definition. >> >> Maybe I have to do this via csopes? but it seems that cscopes just shows >> you where things are defined, whereas semantic will let you jump. >> >> Any ideas on how I can do this, preferably something wtih my .emacs file >> so I don't have to do it each time? >> >> Thanks so much! >> Jai >> > ------------------------------------------------------------------------------ > Don't let slow site performance ruin your business. Deploy New Relic APM > Deploy New Relic app performance management and know exactly > what is happening inside your Ruby, Python, PHP, Java, and .NET app > Try New Relic at no cost today and get our sweet Data Nerd shirt too! > http://p.sf.net/sfu/newrelic-dev2dev_______________________________________________ > cedet-semantic mailing list > ced...@li... > https://lists.sourceforge.net/lists/listinfo/cedet-semantic |