Re: [cedet-semantic] Recommendations for new CEDET & JDEE user for a (mostly) Java project

[Eric M. L. <er...@si...>]

Hi,

Did you you use the GNU global command  "gtags" to create the GLOBAL 
database for your code?  I don't remember if you mentioned doing that or 
not.  You need to create the GTAGS files before global will work on your 
code.

cedet-gnu-global-show-root

will tell you if it is detecting GLOBAL files associated with your 
directory or not.

Eric

On 05/04/2010 05:40 PM, David Ventimiglia wrote:
> Thanks, Eric.  Unfortunately, it resolutely insists on using grep, or
> nothing at all, and I'm afraid there still must be something fundamental
> I'm misunderstanding.  I made customizations in stepwise fashion:
>
> Step 1:  Added to .emacs
> (require 'cedet)
> (semantic-load-enable-code-helpers)
> (global-ede-mode 1)
> Result:  semantic-symref works, but uses grep
>
> Step 2:  Added to .emacs
> (require 'ede-locate)
> (setq ede-locate-setup-options
>        '(ede-locate-global
>          ede-locate-base))
> Result:  semantic-symref works, but uses grep
>
> Step 3:  Added to .emacs
> (require 'semantic-symref-grep)
> (add-to-list 'semantic-symref-filepattern-alist '(jde-mode "*.java"))
> (add-to-list 'semantic-symref-filepattern-alist '(java-mode "*.java"))
> Result:  semantic-symref works, but uses grep
>
> Step 4:  Used ede-new to create a Simple project, which landed in
> %HOME%/.ede/
> Result:  semantic-symref fails, reporting "No references found".
>
> Here's what the file in %HOME%/.ede/ looks like, where the contents of
> :directory and :file just refer to things in my particular project
> directory tree:
> ;; Object cc
> ;; EDE Simple Project
> (ede-simple-project "cc"
>    :name "cc"
>    :directory
> "c:/dev/eng/cc/denali/active/core/app-cc/cc/src/com/guidewire/cc/domain/
> financials/impl/"
>    :file
> "!drive_c!dev!eng!cc!denali!active!core!app-cc!cc!src!com!guidewire!cc!d
> omain!financials!impl!ProjSimple.ede"
>    :targets 'nil
>    )
>
> I must be missing something, but I'm afraid I just can't see what it is.
>
> Best,
> David
>
>
>> -----Original Message-----
>> From: Eric M. Ludlam [mailto:er...@si...]
>> Sent: Tuesday, May 04, 2010 1:26 PM
>> To: ced...@li...
>> Subject: Re: [cedet-semantic] Recommendations for new CEDET&  JDEE
> user
>> for a (mostly) Java project
>>
>> If you use semantic-symref-data-debug-last-result it will show the
>> object that contains the data, and it is named after the tool it uses,
>> like grep or global.
>>
>> Eric
>>
>> On 05/04/2010 01:42 PM, David Ventimiglia wrote:
>>> Thanks, Eric.  I think it might be working for me.  At least, when I
>> do
>>> semantic-symref on a Java function in my project, I get a buffer
> with
>> a
>>> list of references.  It's a little slow, however, and I'm wondering
>> if
>>> it's falling back on Grep and not using my Global tags files.  The
>>> command cedet-gnu-global-show-root does show the right project root,
>>> however.
>>>
>>> Question:  is there a way to verify it's using Global and not Grep?
>>>
>>> Thanks!
>>> Best,
>>> David
>>>
>>>> -----Original Message-----
>>>> From: Eric M. Ludlam [mailto:er...@si...]
>>>> Sent: Sunday, May 02, 2010 5:47 AM
>>>> To: David Ventimiglia
>>>> Cc: ced...@li...
>>>> Subject: Re: [cedet-semantic] Recommendations for new CEDET&   JDEE
>>> user
>>>> for a (mostly) Java project
>>>>
>>>> On 04/30/2010 08:31 PM, David Ventimiglia wrote:
>>>>> 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
>>>>> all
>>>>>> your code.  I'm assuming all the languages you mentioned are in
>> one
>>>>> big
>>>>>> 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
>>>>> symbols?
>>>>
>>>> Ah, good idea with the simple project.  I'd forgotten about that.
>>>>
>>>> If you look in cedet/common/cedet.info in the node:
>>>>
>>>> (cedet.info)Top::>   GNU Global
>>>>
>>>> It lists all the options for enabling GNU Global in a CEDET
> project.
>>>>
>>>>>> As for the symbol references, you can use any of the different
>>> tools
>>>>>> you
>>>>>> prefer, or none.  If you try it (once you have an EDE project
>>>>>> specifying
>>>>>> the root) with the find/grep solution and it is fast enough, then
>>>> you
>>>>>> can consider yourself done.
>>>>>
>>>>> I made these customizations:
>>>>>
>>>>> (require 'cedet)
>>>>> (global-ede-mode 1)
>>>>> (semanticdb-enable-gnu-global-databases 'java-mode)
>>>>> (semanticdb-enable-gnu-global-databases 'jde-mode)
>>>>> (setq ede-locate-setup-options
>>>>>          '(ede-locate-global
>>>>>            ede-locate-base))
>>>>>
>>>>> 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?
>>>>
>>>>
>>>> That means that semantic-symref-filepattern-alist needs to be
>>>> customized.  If you have a good customization, I'll add it to the
>>>> default value.
>>>>
>>>> Probably something like:
>>>>
>>>> (add-to-list 'semantic-symref-filepattern-alist
>>>> 	'(jde-mode "*.java"))
>>>>
>>>> I'll fix the error message to be more obvious.
>>>>
>>>> Of course, this also means that it failed to auto-detect the GNU
>>> Global
>>>> tags file at the root of your project.  Use  M-x
>>>> cedet-gnu-global-show-root to determine if the detection is
> working.
>>>> If
>>>> it fails, then there is something in the Global doc that might
> help,
>>>> since CEDET just calls global with "-pq" options.
>>>>
>>>>> Finally, must one use Global, idutils, locate, etc., to do symbol
>>>>> lookups?  Is it possible just to rely on the CEDET tools alone?
>>>>
>>>> The symref tool relies on at least one external tool, but it can
> use
>>>> find/grep commands to do it, so the other tools are not required,
>> but
>>>> will instead provide better and faster results.
>>>>
>>>>    >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
>>>>
>>>> Semantic only parses the tags (like ctags) and not the contents.
>>>>
>>>>> 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?
>>>>
>>>> Semantic parses it's own tags because tools like global and ctags
>>>> provide only "quickie" information, and take many short-cuts to do
>> so.
>>>> To do what CEDET does with tags, it needs to be much more careful.
>>>>
>>>> Semantic also already has trouble with really huge projects, and
>> Emacs
>>>> Lisp is just the wrong language to implement symbol cross-reference
>>>> database in do the shear size.
>>>>
>>>> Instead, things like Global do a pretty good job on references, so
> I
>>>> use
>>>> those instead, and deal with the inaccuracy of it.  I'm hoping to
>>>> double-check each "hit" with a real analysis to prove that the hit
>> is
>>>> really a reference to a given symbol, and not some side-effect of
>>>> polymorphism or other trick.
>>>>
>>>> Anyway, Global is probably your best bet unless find/grep is fast
>>>> enough
>>>> for you.
>>>>
>>>> Good Luck!
>>>> Eric
>>>>
>>>>
>>>>
>>>
>>>
>>>
> ---------------------------------------------------------------------
>> ---------
>>> _______________________________________________
>>> cedet-semantic mailing list
>>> ced...@li...
>>> https://lists.sourceforge.net/lists/listinfo/cedet-semantic
>>>
>>
>>
> -----------------------------------------------------------------------
>> -------
>> _______________________________________________
>> cedet-semantic mailing list
>> ced...@li...
>> https://lists.sourceforge.net/lists/listinfo/cedet-semantic
>
> ------------------------------------------------------------------------------
> _______________________________________________
> cedet-semantic mailing list
> ced...@li...
> https://lists.sourceforge.net/lists/listinfo/cedet-semantic
>