CEDET

Hi,

  You've got quite a set of questions.

  The version of semantic you are using still has found header file
full names cached in the tag.  If you parse a C file, and a header is
unfound, setting the system path will not fix the problem until you
force a full reparse.

  As of yesterday (imagine that) I removed the caching so that this
wouldn't be an issue anymore.  In addition, there are new decoration
modes that will highlight headers red/yellow and help you through the
process.  Updating CEDET from CVS ought to help.

  The cscope database back-end is in CVS only, and was never finished.
CScope doesn't support all the features semantic needs, so no-one's
worked on in for quite a while.  The ebrowse database might work
better, but I have found it to not be fully reliable.  Setting the
include path is your best bet.

  I don't know what an extended include is.

  For extending EDE with new compilers, the answer is yes, though it
requires some minimal coding skills.  Look in ede-proj-obj.el for the
ede-g++-compiler and -linker variable.  It's just a matter of
declaring the right kind combination of variables.

  If you discover some good compiler declaration combinations that
would be helpful to others, let me know and I can include them.

Eric

>>> public.avatar@... ([AvataR]) seems to think that:
>Good time of day!
>
>Today I try to use emacs with MSVS compiler under wine. All ok, but
>includes.
>I try to append path with windows headers with
>'semantic-add-system-include', but nothing gets. 
>'boviante' output: 
>
  [ ... ]
>
>I try to create cscope database with
>semanticdb-create-cscope-system-database,
>but emacs crash. Then I try to use alraedy created cscope database. It's
>loaded, but seems not used.
>
>What can I do to use extended includes?
>Is there any way to append building models to ede for other compilers,
>and for other build sets like kbuild?
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Microsoft
>Defy all challenges. Microsoft(R) Visual Studio 2008.
>http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>_______________________________________________
>cedet-semantic mailing list
>cedet-semantic@...
>https://lists.sourceforge.net/lists/listinfo/cedet-semantic
>

-- 
          Eric Ludlam:                       eric@...
   Siege: http://www.siege-engine.com          Emacs: http://cedet.sourceforge.net

Thanks for answer. I checkout last CEDET version from CVS. With
codehelpers I can see, that parser has found includes. But now I have
a lot messages in *Message* buffer like 
idle error: "#<buffer *mail*> - Symbol's function definition is void: semantic-lex-spp-string-to-macro-stream"
idle error: "#<buffer *Summary nnmaildir:Incoming*> - Symbol's function definition is void: semantic-lex-spp-string-to-macro-stream"
idle error: "#<buffer *reply to Eric M. Ludlam*> - Symbol's function definition is void: semantic-lex-spp-string-to-macro-stream"
Auto-saving...done

What is this? How can I tune it?

>>> public.avatar@... ([AvataR]) seems to think that:
>Thanks for answer. I checkout last CEDET version from CVS. With
>codehelpers I can see, that parser has found includes. But now I have
>a lot messages in *Message* buffer like 
>idle error: "#<buffer *mail*> - Symbol's function definition is void: semantic-lex-spp-string-to-macro-stream"
>idle error: "#<buffer *Summary nnmaildir:Incoming*> - Symbol's function definition is void: semantic-lex-spp-string-to-macro-stream"
>idle error: "#<buffer *reply to Eric M. Ludlam*> - Symbol's function definition is void: semantic-lex-spp-string-to-macro-stream"
>Auto-saving...done
>
>What is this? How can I tune it?
  [ ... ]

That function doesn't exist anymore.  You probably got half a set of
changes I checked in this afternoon.  You may need to resync from CVS
and do a full rebuild.

Eric

-- 
          Eric Ludlam:                       eric@...
   Siege: http://www.siege-engine.com          Emacs: http://cedet.sourceforge.net