Hm, managed to resolve this by appending my project dirs onto the auto-mode-alist with c++-mode so that headers would open in c++-mode rather than c-mode; not sure why adding the system includes for c-mode also didn’t have the same effect, I’d assume they would.
I have a quick question regarding system include paths. I have an ~/.emacs file with a variety of lines of the form:
;; CEDET / Semantic / Xbox 360 system includes
(semantic-add-system-include "c:/Program Files (x86)/Microsoft Xbox 360 SDK/include/xbox" 'c++-mode)
If I open a file outside a project root, it will find headers in the system include dirs just fine. However if I open up a file inside an ede-cpp-root-project, I’ll get tons of unparsed includes. When I look at their summary page I’ll see something like below. Is the ede-cpp-root-project somehow masking the Semantic system include? Do I need to somehow pass my Semantic system include list to the ede-cpp-project-root as :system-include or some such? I tried doing this with semantic-dependency-system-include-path but it didn’t seem to work properly. I’ve also tried duplicating all my semantic-add-system-include calls for c-mode as well as c++-mode but that didn’t seem to work either.
Include Summary for File: d:/jobqueue/xenon/jobqueue_xenon.h
This file contains 17 tags, 3 of which are includes.
Unknown Includes: 2
Unparsed Includes: 0
Parsed Includes: 1
Include Path Summary:
This file's project include search is handled by the EDE object:
Buffer Target: #<ede-cpp-root-target d:/jobqueue/xenon/>
Buffer Project: #<ede-cpp-root-project jobqueue>
Backup in-project Locator: #<ede-locate-base Loc>
EDE Project system include path: Empty
This file's system include path is:
All unknown includes:
There are currently no includes found recursively.