WEBKIT_EXECUTABLE(DumpRenderTree)
Created attachment 395591 [details] Patch
Created attachment 395596 [details] Patch
Created attachment 395609 [details] Patch
Created attachment 395624 [details] Patch
Created attachment 395625 [details] Patch
Comment on attachment 395625 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=395625&action=review > Tools/DumpRenderTree/CMakeLists.txt:45 > + ${PAL_FRAMEWORK_HEADERS_DIR} Do you need to add PAL_FRAMEWORK_HEADERS_DIR? Why don't you use WebKit::PAL?
(In reply to Fujii Hironori from comment #6) > Comment on attachment 395625 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=395625&action=review > > > Tools/DumpRenderTree/CMakeLists.txt:45 > > + ${PAL_FRAMEWORK_HEADERS_DIR} > > Do you need to add PAL_FRAMEWORK_HEADERS_DIR? Why don't you use WebKit::PAL? I think we need a macro that handles the fact that every WEBKIT_FRAMEWORK could be SHARED/STATIC/OBJECT and propagate interfaces correctly. That's a temporary kludge around it.
Committed r259617: <https://trac.webkit.org/changeset/259617> All reviewed patches have been landed. Closing bug and clearing flags on attachment 395625 [details].