Eric M. Ludlam wrote:
> The best place to start is with the command
> semantic-c-describe-environment. It may list some EDE object that will
> be doing the file finding for your subproject, depending on what it
> You can also right click on a header file, and select 'what is this'
> from the menu, and it might provide some (similar) hints.
> In general, it is better to use an ede project type, even if it is
> ede-cpp-root, to define the base of your project, as it will do a better
> job of finding in-project header files.
that did the trick, thanks
> It may also be that there is a bug with includes with directory paths in
> them for your case.
> On 04/05/2010 03:05 PM, Christian Thaeter wrote:
>> We've split our source directory into sub-parts (but not sub-projects).
>> Cross-includes are deliberately prefixed with the directory there.
>> This setup is like following:
>> the project root is at
>> then there is a ./src dir which contains the subdirs for each part
>> semanticdb-project-roots is set to ("/home/ct/src/project/")
>> now when I
>> #include "lib/something.h"
>> semantic tells me this is a 'Unknown Include', just
>> #include "something.h"
>> would work for semantic but is not the way its intended to be used and
>> of course breaks the build setup.
>> I suspect this is some bug in the way semanticdb looks up the includes,
>> any idea how to shed some light on this?
>> I'm using cedet-1.0pre7 on debian lenny with emacs32 from backports.org.
>> Btw: I tried ede but that has servere problems with our project setup,
>> thats non-recursive building with one top-level Makefile.am which in
>> turn includes Makefile.in from the sub dirs. Fixing this looks like a
>> challenge to me, If you are interested I can provide more information :).
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> cedet-semantic mailing list