Eita Karasawa

Sorry for my late reply. I have been testing variously. I could not get the results I expected with --debug option. There is many report as "severity="debug"" but there is still this issue and no more new information. I will give up on solving this issue... Because I can't prepare the minimum environment for this issue and I can't show all my environment publicly to get advice. I appreciate your cooperation. Thank you.

I use -v and --debug options but there is no changes. So I modified command as follows. $ ./cppcheck --enable=all --platform=win64 --include=./Application_header.h C:\source -> 57 reports When I used the relative path from the check-folder, there were 57 reports. Also, the include item(Includes:) of the log was blank. Checking C:\source\test.cpp ... Defines: Includes: Platform:win64 Am I correctly using --include option?

Certainly, it seems to have been fixed in a minimal environment. Likewise, I applied it to my development environment as follows. [Application_header.h] #if defined(PLATFORM_0) typedef char BYTE; #elif defined(PLATFORM_1) typedef int8_t BYTE; // define BYTE as an signed char #else #define BYTE __int8 #endif [command and result] $ ./cppcheck --enable=all --platform=win64 --include=C:/source/Application_header.h C:\source -> 0 reports $ ./cppcheck --enable=all --platform=win64 C:/source -> 57 reports...

Certainly, it seems to have been fixed in a minimal environment. Likewise, I applied it to my development environment as follows. [Application_header.h] #if defined(PLATFORM_0) typedef char BYTE; #elif defined(PLATFORM_1) typedef int8_t BYTE; // define BYTE as an signed char #else #define BYTE __int8 #endif [command and result] $ ./cppcheck --enable=all --platform=win64 --include=C:/source/Application_header.h C:\source -> 0 reports $ ./cppcheck --enable=all --platform=win64 C:/source -> 57 reports...

Certainly, it seems to have been fixed in a minimal environment. Likewise, I applied it to my development environment as follows. $ ./cppcheck --enable=all --platform=win64 --include=C:/source/Application_header.h C:\source -> 0 reports $ ./cppcheck --enable=all --platform=win64 C:/source -> 57 reports (This issue still remains.) About 50 cases of warning/style were reported before change, but there were 0 reports after change. Not only this issue, it seems that all reports are no longer being reported....

Certainly, it seems to have been fixed in a minimal environment. Likewise, I applied it to my development environment as follows. $ ./cppcheck --enable=all --platform=win64 --include=C:/source/Application_header.h C:\source -> 0 reports $ ./cppcheck --enable=all --platform=win64 C:/source -> 57 reports (This problem still remains.) About 50 cases of warning/style were reported before change, but there were 0 reports after change. Not only this issue, it seems that all reports are no longer being...

Certainly, it seems to have been fixed in a minimal environment. Likewise, I applied it to my development environment as follows. $ ./cppcheck --enable=all --platform=win64 --include=C:\source\Application_header.h C:\source -> 0 reports $ ./cppcheck --enable=all --platform=win64 C:\source -> 57 reports About 50 cases of warning/style were reported before change, but there were 0 reports after change. Not only this issue, it seems that all reports are no longer being reported. Did I make a mistak...

What exactly do you want to fix? I want to treat "BYTE" as a signed char on all platforms and fix all style and warning with Cppcheck(platform=win64). Is it impossible with windows.cfg (=win64)? Thank to you, I've just understood that "__int8" is treated as char (=unsigned) according to windows.cfg. (I refer https://github.com/danmar/cppcheck/blob/master/cfg/windows.cfg) I thought that "BYTE" is signed data type, because I use "int8" as signed char and "unsigned int8" as unsigned char in my envi...