Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Eric M. Ludlam <eric@si...> - 2008-12-30 02:14:25
>>> kristof.ralovich@... seems to think that:
>I am using cedet from current CVS. I am not using EDE, but cmake.
>Could someone tell me how to make semantic know about (and parse,
>etc.) my c++ project's header files? The project and the headers are
>in eg.: /proj, /proj/include respectively. I have tried
>semantic-add-system-include, but I couldn't make it work for me.
[ ... ]
It would be useful if you joined the mailing list to post questions.
I don't always find the quarantined messages.
You can wrap your C++ project in a simple EDE wrapper. See the
ede-cpp-root project type in either the CEDET general documentation,
the ede documentation, or in ede-cpp-root.el comments itself. You
probably want to do something like this:
;; (ede-cpp-root-project "NAME" :file "FILENAME"
;; :include-path '( "/include" "../include" "/c/include" )
;; :system-include-path '( "/usr/include/c++/3.2.2/" )
;; :spp-table '( ("MOOSE" . "")
;; ("CONST" . "const") ) )
where FILENAME is something like /dir/to/my/project/CMakefile
or some other file at the root of your project.
This is probably the best way to apply include paths, extra CPP macros
you need, and system include paths there is for C++. It wraps
everything up in a simple way.
If you feel particularly brave, you can create a new EDE project type
The system include path is used for <include.h> type includes, not
"include.h" type includes.
Eric Ludlam: eric@...
Siege: http://www.siege-engine.com Emacs: http://cedet.sourceforge.net