fix: use both absolute and relative header paths in header matching by Tal500 · Pull Request #362 · cppcheck-opensource/simplecpp

This fix an issue of importing the same header by different addresses.
The issue is trickier than seems, because if a user used the include dir flag `-I...` with an absolute path, then every matched header was detected to be absolute, but if the import was a relative import to the source file and the source file isn't with an absolute path, than the header is identified by the combined relative path.
See https://sourceforge.net/p/cppcheck/discussion/general/thread/c01f80556b/

Tal500 changed the title fix: always use absolute (and simplified) header path whenever possible fix: use both always and relative header paths in header matching

Tal500 changed the title fix: use both always and relative header paths in header matching fix: use both absolute and relative header paths in header matching

Tal500 deleted the absolute-path-header branch

danmar added a commit that referenced this pull request

danmar added a commit that referenced this pull request

Tal500 pushed a commit to Tal500/simplecpp that referenced this pull request