WTF is very tricky. These headers are copied to BuildDir/usr/local/include/wtf. And source files start using it... That causes problems. Based on how you include headers (I believe this relies on "XXX.h" and <wtf/XXX.h> with different header search paths), the compiler includes the same files twice with difernt paths (Source/WTF/wtf/XXX.h and BuildDir/usr/local/include/wtf/XXX.h). And it causes compile errors. The example is wtf/text/StringView.h. When I changed this ifndef guard to pragma once, it causes compile error(https://bugs.webkit.org/show_bug.cgi?id=166676#c5). And I reverted this part. And we can see similar problems https://bugs.webkit.org/show_bug.cgi?id=164194#c4. But this tricky problem should be fixed. And we should change WTF headers' ifndef guard to pragma once.
This is my guess, but I think we should use "XXX.h", "text/XXX.h" styles in WTF instead of using <wtf/XXX.h> in WTF.
(In reply to Yusuke Suzuki from comment #1) > This is my guess, but I think we should use "XXX.h", "text/XXX.h" styles in > WTF instead of using <wtf/XXX.h> in WTF. I think that the problem is that <wtf/XXX.h> goes to the build directory while "XXX.h" goes the source directory. We should consistently use "XXX.h" in WTF for WTF headers. Of course, outside of WTF, we should use <wtf/XXX.h>.
(In reply to Yusuke Suzuki from comment #2) > (In reply to Yusuke Suzuki from comment #1) > > This is my guess, but I think we should use "XXX.h", "text/XXX.h" styles in > > WTF instead of using <wtf/XXX.h> in WTF. > > I think that the problem is that <wtf/XXX.h> goes to the build directory > while "XXX.h" goes the source directory. We should consistently use "XXX.h" > in WTF for WTF headers. Of course, outside of WTF, we should use <wtf/XXX.h>. Might another issue be that we're using XXX_INCLUDE_DIRECTORIES when it should be XXX_PRIVATE_INCLUDE_DIRECTORIES?
If we use XXX_PRIVATE_INCLUDE_DIRECTORIES, we go back to situation where internal include paths of XXX are added to other targets. See https://bugs.webkit.org/show_bug.cgi?id=165686
(And in WTF we already use private includes)
Created attachment 333308 [details] Patch WTF headers are all copies now so this might actually work now. Lets see what the bots say. https://pypi.python.org/pypi/guardonce was used to do the conversion.
WPE came back ok and I'm pretty sure the other CMake ports are going to come back green. So the reason those are going to come back green is that the headers are installed into WebKitBuild\Release\DerivedSources\ForwardingHeaders\wtf\*. This directory is not included within the WTF include directories. Also Source\WTF is not an include path for the dependent projects. The reason Apple Cocoa ports are coming back red is that within the xcode projects WTF is installed into /usr/local/include/wtf which for sure is on the system path. https://trac.webkit.org/browser/webkit/trunk/Source/WTF/Configurations/CopyWTFHeaders.xcconfig#L24 So if all the headers used relative paths internally this could go forward. If we flatten the headers in WTF then this would also work. On the CMake side its simple enough to flatten but with the Apple Cocoa side its a bit more murky. The command within the xcode project is at https://trac.webkit.org/browser/webkit/trunk/Source/WTF/WTF.xcodeproj/project.pbxproj#L1393 and looks to be an rsync. There's a stack overflow question that looks like it might do the trick, https://stackoverflow.com/questions/14661033/rsync-recursively-sync-all-files-while-ignoring-the-directory-structure, but I'm not familiar enough with the Mac side to take a real stab at it.
I'm fixing this in https://bugs.webkit.org/show_bug.cgi?id=190527
*** This bug has been marked as a duplicate of bug 190527 ***