Oliver Stöneberg
Oliver Stöneberg
The current behavior of the lookup of external files is wildly inconsistent for each type and depends on if you are using the GUI or CLI. This can be mostly...
A case against supporting CWD in the lookup (from https://github.com/danmar/cppcheck/pull/7639#discussion_r2192049596): "It will look in the folder you run Cppcheck from. So on Linux, if you have files in your user...
> Maybe I missed it? I do not see an alternative suggestion yet how configuration files would be found in the project folder. It looks relative to the project file....
> great. that is fine for me. so look in the project file folder first if that exist. and then look in CWD folder.. I am still a bit torn...
I was trying to make the object local instead of a class member but as it is being used by `reportErr()` that is unfortunately not possible. Even I did not...
I think I might need to add some builddir-related tests first.
> I am still a bit torn of supporting CWD. Because if you invoke the tool you might do so from a random path since the executable is in `PATH`....
The fact that `CppCheck` object owns the `Settings` object complicates things. That also needs to be resolved first it seems...
This exposes an issue with the ignored paths not matching when the slashes differ from the given path.
I filed https://trac.cppcheck.net/ticket/12972 about the issue with the mismatching slashes.