System omniscience libraries: confused about setup

Hello,

I have a few directory trees which together comprise source code for the
majority of my system (kernel, userland, etc).  I would like semantic to
be aware of these sources, such that I can jump to tag definitions,
implementations, etc, similar to the functionality that is available for
Emacs Lisp.  Note, that I want to be able to jump to *implementations*
(source content) as well as definitions (header content).  Note also
that these are directory trees, with many nested folders.

My understanding is that an omniscience database is appropriate to this
task.  After much digging around (on the web, this list, info manual,
source code, etc), I have found various references and instructions, but
have been unable to get anything working.  It's all too scattered at
this point to easily list what I've tried and what results that has
yielded, so let's start simple, from scratch...

What is the correct way to go about this?  Should I be trying to use an
omniscience database?  How do I generate and use such a database?  Let's
assume for now that I'm working with C code, and that the directory tree
is located at /usr/src/motif/git.

If it matters, I'm using Emacs 24/25 with CEDET 2.0.



-- Matthew R. Trower



P.S.  In case I'm *really* going into left field here, the original
problem I was trying to solve was this: semantic understands about my
system headers in /usr/include, but those are only definitions.  I know
of no easy way for me to jump to the corresponding implementation, even
though the source is available elsewhere on my system...

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot