On 02/20/2011 06:24 PM, Andrea Crotti wrote:
> Il giorno 20/feb/2011, alle ore 21.54, David Engster ha scritto:
>> Works for me.
>> Please try the latest development checkout from bzr, which you can get
>> bzr checkout bzr://cedet.bzr.sourceforge.net/bzrroot/cedet/code/trunk cedet
>> You should also delete all cached tags in ~/.semanticdb before trying
>> the new CEDET version.
> I removed the cached tags and it works already, strange but well, better :)
> But one thing I don't quite get.
> Suppose I have those variables
> (global-ede-mode t)
> (setq ede-locate-setup-options '(ede-locate-global ede-locate-locate ede-locate-idutils))
> (ede-linux-project "mylinux"
> :file "$HOME/code_study/linux-2.6")
In theory, you don't need to specify the location of a Linux project.
It should auto detect. It does so by looking for scripts/ver_linux, so
if that changes, it won't work anymore.
> In theory that should be enough to be able to work and be able to jump everywhere from the source code?
> How do I know what is the include path which is being used at the moment?
The linux project type has a default include path that should be ok. If
not, it should be updated. The ede locate libraries like idutil expect
their cache files in the root of the EDE project.
> And with more locate function used is it possible to see who gave the answer?
> I find a bit strange the definition of a project:
> (ede-cpp-root-project "NAME" :file "FILENAME"
> Because I don't get what the filename should be.
> Now I used the top-level directory and seems to work anyway, but is that correct?
> If I'm supposed to used the directory maybe "file" should be removed to "path" or "directory" imho...
It can be any file in your project that will mark it distinctly. It
could be a Makefile or something. It is used to see if your project
gets deleted or in a bad state. I think just using "." will work if you
have not top-level files in your project.