Re: [CEDET-devel] bypass GNU global code if GNU global programs are not in path?
Brought to you by:
zappo
From: Eric M. L. <eri...@gm...> - 2011-11-16 01:04:09
|
On 10/18/2011 04:05 PM, David Engster wrote: > emacs writes: >> I'm trying to setup CEDET with example files (including GNU global >> database files created by gtags program) so that my colleagues can test >> drive cedet and other elisp tools. Some people have gtags in their >> path, but some don't. So if those without gtags in their PATH loads one >> of my C++ file with associated GNU global database files, then cedet >> seems to detect the database files and tries to run 'global' program to >> parse them. If my colleagues without gtags in their PATH tries out my >> examples, cedet signals error when it fails to launch 'global'. > > Only having the Global database file(s) in the project shouldn't by > itself lead to CEDET trying to actually use it. You still have to > explicitly activate it by using > > (semanticdb-enable-gnu-global-databases 'some-language-mode) > > If you really see that CEDET calls global although the above line was > not called, then I think that would be a bug, but at the moment I cannot > see that behavior. Do you also provide special init files for CEDET for > your colleagues? If so, I think you should check for global there. I'm worried that a silent ignore would give folks a false sense of success when trying ti get gnu-global support working. Perhaps the best solution for a generic installation is: (if (cedet-gnu-global-version-check t) ; dont error (semanticdb-enable-gnu-global-databases ... and thus not install anything if it isn't there. Eric |