Visual studio headers cause errors about sourcetrail HOT 2 CLOSED

@jaked122: To find out where the file is located just hover the file name "combaseapi.h" and Coati will display the file's path.

First of all: These errors should't affect Coati's code analysis.
I can understand that this is bothering you, so i did some research. If you are having errors that state something like use of undeclared identifier 'char16_t' they can be fixed. These types are builtin for the MSVC compiler and there is a compatibility mode for clang to cope with these types as well. It can be enabled via compiler flags. They can be set by manually editing the *.coatiproject file. Just open the file in a text editor and add the following tags as child nodes of your <source> node:

<compiler_flags>
    <compiler_flag>-fms-extensions</compiler_flag>
    <compiler_flag>-fms-compatibility</compiler_flag>
    <compiler_flag>-fms-compatibility-version=19.00</compiler_flag>
</compiler_flags>

Besides the errors mentioned above, it doesn't fix the IUnknown error you posted. There is a discussion to add this magic microsoft define to the clang ms compatibility mode. So this error is probably gone when we upgrade Coati to the upcoming clang release. I will close this issue for now but it can be reopened if this stays an issue in the future.

from sourcetrail.

@jaked122: As a result of your post I just filed 2 new feature requests:
#37 Set compiler flags via GUI: It seems like compiler flags are becoming important right now. Going into the XML for manual edits is not the best way to go ;)
#38 Show fatal errors of code analysis: These are the errors you should worry about. Coati needs to display if there are any of these.

from sourcetrail.