I have the same kind of problem with the C++ Analyzer.
None of my defined include paths can be resolved so far. I tried to define include
paths via "Directories..." and also via "Bases..." by defining an own include project.
Even if i click on an include path in an cpp-file the referenced file can be opened but not included!
That means that the directory structure is created properly and can be accessed, but the include
mechanism od the C++ Analyzer has a big problem...
Please poste an reply or write me an email if you have any solution!
I have a lot of experience with the C++ Analyzer. It does work very well, but there
are a few gotchas. It is a C++ compiler so it does need the full closure of the program.
It does incremental compilation, so if you make a change it does not always know how much
to compile, you may need to do a clean build. It is very smart in that it can compile a header
(.h file) without the body (.cpp) file. This is what leads to inclusion problems because many
people (Microsoft corp) set up the cpp files to have the inclusion of headers in some order.
The C++ Analizer does have workaround for this problem (setting files to type 3).
Please contact me directly so we can take your problems off-line.
(you can also work through tech support).
The Rose C++ Analyzer is "feature complete" and has been around for a long time, therefore there have
not been any changes lately. It is a 16 bit application originally created for Windows 3.1 circa 1994.
It has had lots of bug fixes since then but no major upgrades. It has changed its output to work
with Rose file formats.
It is a C++ compiler, and ANSI C++ has not changed much. The analyzer only analyzes and compiles the
structure (header files) so changes in the C++ bodies do not matter.
The analyzer works well, and there is no reason to mess with code that works. I have personally used it
to analyze a project with over 20,000 classes and know people that have used it for 50,000 class projects.
It correctly analyzes complex templates.
Sometimes it does bad things to badly written C. It does poorly with plain C, as there are no classes and lots
of globals.
Poorly stuctured MACROs can be a problem, but there are workarounds.
Most of the problems that I see with the analyzer are non-standard compiler specific deviations from C++
(That is not a problem with the analyzer, it is a problem with the code)
We have workarounds, MACRO define the problem to blank.