New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WPE] Checkout a specific version of Cog instead of master #7508
[WPE] Checkout a specific version of Cog instead of master #7508
Conversation
EWS run on previous version of this PR (hash b103e74) |
b103e74
to
87d52fd
Compare
EWS run on previous version of this PR (hash 87d52fd) |
I finally noticed that the EWS is broken:
So yeah, that plan is not going to work. |
It seems the build failure is because you used as version So, instead of using a tagged version I think we should use a git hash of the last version on master, and update this periodically as needed (the build breaks or someone remembers to update it). So try using |
Secondary goal here is to use a version of cog that can build #5944, so using anything on the cog master branch will not be possible unless we're willing to make cog depend on WebKit pull request branches. So I'll prepare a cog side branch and switch WebKit to use that for now. Not sure how soon I'll get to this, though. |
Maybe an idea is to patch the Cog Meson build system to allow manually selecting which API to use and pass the desired parameter to Cog/Meson from WebKit/CMake |
That won't work either. If we use the wpe-webkit-2.0 API then we have a circular dependency between cog and WebKit when making API changes. If we use the wpe-webkit-1.1 API, like I tried to do above, then the build will fail because it doesn't exist anymore in WebKit. I see two workable options:
My preference is option 2 because that would be easier for WebKit development, but it risks that we forget to keep cog in good shape. |
So for this pull request, let me switch to using the latest release of cog. I'll open a separate pull request to temporarily disable cog. I think perf tests can use MiniBrowser instead, at least for the next two months, right? |
https://bugs.webkit.org/show_bug.cgi?id=249034 Reviewed by NOBODY (OOPS!). Igalia wants to start running performance tests, but performance test results will be inconsistent if the version of cog may be different from one day to the next. A specific commit should be used instead. The downside of this change is we now have to remember to update the Cog version to use in a rather unobvious place, Tools/PlatformWPE.cmake, which is not something that we will remember to do on a regular basis. We need a better way to handle this, such as adding it to the Cog release process. * Tools/PlatformWPE.cmake:
87d52fd
to
02eb578
Compare
EWS run on current version of this PR (hash 02eb578) |
Switched to 0.16.1. Hopefully the EWS will like this.
|
Not really. Using cog is a must. |
See #7508 (comment) |
I see. I see three possible solutions to this:
I can see pros&cons for each solution. But given that modifying the API is not something usual maybe the less bad option for now is to use cog side branches. Perhaps we can name the branch in Cog something like: WDYT? |
I'm fine with any of the three options, but I suspect option 1 will be easiest. Option 3 (import into Source/ThirdParty) would require resurrecting cog's CMake build system. Surely that's doable, but this is a temporary problem and it makes sense to go with the simplest solution. |
Closing this. I will do this directly in #5944 instead. |
02eb578
02eb578