On 8/7/15 4:59 PM, Alex Christensen wrote:
Right now, the Mac and Windows ports have TestWebKitAPI built as a single
executable. Tools/TestWebKitAPI/CMakeLists.txt currently creates many
executables to test things in groups. I want to make the Windows port build
everything with CMake at the beginning of next week, but I’m not sure how to
proceed and build TestWebKitAPI. I see 3 options:
1) Change the GTK and EFL ports to build and run one TestWebKitAPI executable.
2) Change the Windows and maybe eventually Mac ports to build many
TestWebKitAPI executables (TestWTF, TestJavaScriptCore, etc.). It would be
easiest for me if this were done after removing the Visual Studio build system.
3) Maintain different CMake builds of TestWebKitAPI building one or many
executables. This would probably be the least invasive option.
I consider each option to have about equal merit, but I think I need input from
the GTK and EFL maintainers before proceeding. Either way, there would be
slight differences between the ports because of things like WebKit2 not
existing on Windows right now, so I suggest the third option.
I have the feeling [2] may be the most useful for the project.
Having one binary per test suite seems better to parralelize (some of)
them. It may also reduce flakiness due the reduced dependencies.
Benjamin
_______________________________________________
webkit-dev mailing list
[email protected]
https://lists.webkit.org/mailman/listinfo/webkit-dev
