Clang code model & analyzer processing include paths incorrectly on qmake project.

Using Qt Creator 4.7.2 and 4.8.0 on Windows 10 with Visual Studio 2017 and Qt 5.11.3, having problems with clang code model processing paths.  In project, I have many absolute paths to include files like "INCLUDEPATH += /usr/local/mystuff".  These projects are used with many different Qt platforms and using a *nix path like "/usr/local/mystuff" works well, with no build issues, even on Windows.  However, with the new clang stuff, the path is being interpreted as a relative path to the current project build path instead of an absolute path back from root.

This results in many "xxx.h" file not found errors and hundreds of edit-time clang error messages even though the project will build 100% successfully.  I can fix it by specifying "c:/usr/local/mystuff" instead, but this is not cross-platform.  If you perform a analyze/clang and look in the "app output" window, you will see the absolute paths incorrectly appended to the current project folder.  Note that in my project file, I am not using "$$PWD/usr/local/mystuff".   Therefore, an absolute path back to root should be processed correctly in Windows, as it is in Linux and the other platforms??