Thanks, Eric. I've a few, more-specific questions spliced in below.
> The basic strategy is to get an EDE project pointing to the root of
> your code. I'm assuming all the languages you mentioned are in one
> mega-project. That top level project then needs to know about all the
> targets. For simplicity sake, you could have one target per language
> type, or more detailed, one target per language/directory.
So far, I just started with ede-simple-project, which I created with the
command ede-new while visiting a Java file buried deep in that part of
our source-tree. This put a file in my $HOME/.ede directory defining
that ede-simple-project. I also have run GNU Global in my project root.
What do I do now to enable completion, lookup, and cross-references for
> As for the symbol references, you can use any of the different tools
> prefer, or none. If you try it (once you have an EDE project
> the root) with the find/grep solution and it is fast enough, then you
> can consider yourself done.
I made these customizations:
But when I invoke the command semantic-symref-symbol on some symbol in a
Java file, I get the message:
semantic-symref-tool-grep - Needs to be configured for jde-mode
What does this mean?
Finally, must one use Global, idutils, locate, etc., to do symbol
lookups? Is it possible just to rely on the CEDET tools alone? What I
mean is, I gather that semantic is parsing and caching the tags for,
say, the Java files that I visit. Is it possible to have semantic parse
ALL my Java source files ahead of time (a la Global, idutils, ctags,
etc.), then just use semanticdb to support completion, lookup, and
cross-referencing? This isn't a huge deal, but I'm trying to evangelize
Emacs+CEDET+JDEE at my company, which is a Windows shop, and the more
external tools I have to integrate (like finding Windows versions of
Global, idutils, etc.), the harder that sell becomes. Or, would it
simply be too much of a performance hit to ask semantic to do what
Global et al are optimized to do very fast?