Hi Joachim, On 12/19/22 10:26, Joachim Reichel wrote:
severity 1026302 wishlist thanksHi Alex,Similar to GCC's -isystem to specify a path to check for system headers, it would be very useful to tell cppcheck where to find system headers. I'm writing a library, whose headers include eachother using <> since it's intended to be used as a system library. However, for building (and linting) it, I need to tell the compiler (and linters) that the includes are not really system includes.I don't quite understand why you want/need -isystem for cppcheck. Is it just the minor inconvenience that you have to replace possible "-isystem" occurrences in your CFLAGS etc. by "-I"? Or is it the fact -isystem directories will be processes after -I directories?Also I don't understand "I need to tell ... are not really ..." in the last sentence. What does that mean in terms of actual compiler/cppcheck arguments? If you need to do something special (?) for the compiler, why is it not ok to do the same for cppcheck (maybe with s/-isystem/-I/)?It might help if you provide more details.
Sorry, my mistake. I was getting a warning that cppcheck(1) wasn't finding some headers, and I had assumed it was my own headers, but it seems it was libc headers, which it is fine if it doesn't find them. So invalid bug report, I guess. :)
Cheers, Alex -- <http://www.alejandro-colomar.es/>
OpenPGP_signature
Description: OpenPGP digital signature
