Andreas Mohr

Also, cppcheck possibly doesn't provide a Show Includes (MSVS)-type (or: gcc -H) log functionality - which however likely is a crucial functionality when trying to re-create a functionally completely equivalent parsing tree within a sufficiently complex source environment. So you may have a case of some important infrastructure define (think _M_X64 or _MSC_VER stuff) not yet being -D:d, and this resulting in some infrastructure #include not getting done, thus getting a completely mismatching traversal...

Also, cppcheck possibly doesn't provide a Show Includes (MSVS)-type (or: gcc -H) log functionality - which however likely is a crucial functionality when trying to re-create a functionally completely equivalent parsing tree within a sufficiently complex source environment. So you may have a case of some important infrastructure define not yet being -D:d, and this resulting in some infrastructure #include not getting done, thus getting a completely mismatching traversal of #include hierarchy (mismatch...

Hello all, when initially doing a cppcheck invocation on a more complex project, cppcheck keeps spewing unknownMacro errors. Checking Foo\Bar.cpp ... Foo\Bar.h:108:2: error: There is an unknown macro here somewhere. Configuration is required. If DECLARE_MESSAGE_MAP is a macro then please configure it. [unknownMacro] This error message is sufficiently confusing/misleading/imprecise since in most cases this is a case of letting cppcheck know where to resolve include paths to the required headers which...

Correction: hardcoding: vcproj2cmake_recursive.rb: prefer using official toolkit helpers.

Correction: consistency: prefer Array.collect().

Correction: consistency: stale logging.

Bug fix: IMPORTANT: consistency: fix IDL breakage (incomplete rename of v2c_target_midl_compile function).

Bug fix: IMPORTANT: consistency: vcproj2cmake_func.cmake: fix wrong function naming.