Re: [CEDET-devel] Proper way to add project-specific system include paths

[Eric M. L. <er...@si...>]

>>> "Gooch, Allen" <ag...@bi...> seems to think that:
>With cedet built from CVS sometime last week. In my .emacs file I have the =
>following:
>
>(load-file "/usr/local/src/cedet/common/cedet.el")
>
>;; NOTE: If I uncomment the following three lines the boost include path is=
> honored and parsed
>;; (semantic-add-system-include "/usr/include" 'c++-mode)
>;; (semantic-add-system-include "/usr/include/c++/4.3.2" 'c++-mode)
>;; (semantic-add-system-include "/usr/local/include/boost-1_38" 'c++-mode)
>
>;; Enable EDE for a pre-existing C++ project
>;; NOTE: If I instead configure with :system-include-path in my project the=
> boost include path is NOT honored nor parsed
>"~/sandboxes/sb1/mmo1/global/External/Boost/boost_1_38_0"))
>(ede-cpp-root-project "TimerTestProject"
>                      :name "TimerTestProject"
>                      :file "~/development/playground/TimerTimerProject/CMa=
>keLists.txt"
>                      :system-include-path '("/usr/include" "/usr/include/c=
>++/4.3.2" "/usr/local/include/boost-1_38"))
>
>Reading the docs, I would expect the way I set up my root project to correc=
>tly find and parse the boost header files, but that is not the case.  What =
>is the proper way to do this with CEDET?
  [ ... ]

Hi,

  Your config looks fine to me.  I double checked my testing project
for ede-cpp-root, and it works for me.  If in one of your C++ files
that uses boost, if you run:

 M-x semantic-c-describe-environment

 it will list out a bunch of different C related configuration items.
One of the sections looks like this for me:

------------
Include Path Summary:

  This file's project include is handled by:
   #<ede-cpp-root-target /home/eric/TEST/subdir/>
  with the system path:
    /usr/include/X11

  This file's system include path is:
    /usr/include/
    /usr/include/c++/3.2.2/
    /usr/include/c++/3.2.2/i386-redhat-linux/
-------------

So for me, I was testing with /usr/include/X11.  In this case, it
correctly identified My X header as being found.

For the include path items /usr/include, and /usr/include/c++/###, it
should be sufficient to let the gcc auto-config handle those.  If you
look in the path summary generated above, if those paths also show up
in the system include path, then you don't need them associated with
your project.

Lastly, I'll guess you have the include file highlighting enabled.  If
you right-click on an include, there are a few options.  One of which
will also describe include paths and such.  It didn't show the EDE
system path, so I added that tonight, but the data is the same as
semantic-c-describe-environment.

If this doesn't help, I can try and dig up some more debugging tricks
for this issue.

>>> "Gooch, Allen" <ag...@bi...> seems to think that:
>I would like to disable the thin blue line that appears by default above
>new scopes, functions, typedefs, etc., that you can see in the image at
>http://cedet.sourceforge.net/img-gen/ecb.png.

In the Senator menu, there is a "Tag Decorations" menu item, from
which you can disable the tag boundary mode.  You can use
`semantic-toggle-decoration-style' to toggle a particular decoration
type by name.

>Also, I don't want to clutter up the devel list with user questions but
>didn't see any cedet-user list.  What is the appropriate list for user
>questions?
  [ ... ]

This is a fine mailing list for questions, or the cedet-semantic
mailing list.  In either forum, these are useful questions that often
expose miss-understandings in the doc pages, or in the interfaces.

Good Luck
Eric

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