feat(engine): relocatable WebKitGTK build — self-contained engine loads via $ORIGIN - #4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The start of the "ship our own engine" pipeline — and the first milestone is proven.
tools/engine/build-webkitgtk-linux.shrelocates the system WebKitGTK + its full shared-object closure into a self-contained engine tree, rewriting every RPATH to$ORIGIN(viapatchelf) and copying the WebKit helper processes..github/workflows/build-engine.ymlbuilds it on Ubuntu and proves it loads: with noLD_LIBRARY_PATH, the engine's dependency closure resolves entirely via$ORIGIN. CI result: 125/125 libraries loaded from the relocated engine (webkitgtk-6.0-2.52.3-built1-linux-x64).WEBKIT_EXEC_PATHadded to the loader env so a pinned engine spawns its own helper processes (WebKitNetworkProcess/WebProcess/GPUProcess), not the system's — render-ready.This upgrades the alpha-2 proof (which relocated 2 system libs) to a genuinely self-contained, portable engine that loads with zero reliance on the host's WebKitGTK.
Next (follow-ups): a render proof (it loads; rendering a page via the relocated helpers under xvfb is the next iteration), cross-distro portability (build on an old-glibc base), and signing + hosting the artifact to a feed.
tools/is outside the lint/typecheck scope, so the main validate is unaffected.🤖 Generated with Claude Code