severity 1026302 wishlist thanks
Hi 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.
Would you please add such an option?
I myself will not add such an option. This a feature request for upstream. While I can forward your request (as I do with bug reports), it probably makes more sense if you report it directly upstream yourself. For such a request I'd expect more questions etc. from upstream and if you report the feature request yourself, then it's easier for you to argue for your case, instead of relying on me passing messages back and forth.
Adjusting severity to "wishlist" (feature request). Best regards, Joachim
