[Webkit-unassigned] [Bug 256471] Minibrowser starts the network process but the web process crashes

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=256471

--- Comment #24 from Mero <p357htrnomet at ezztt.com> ---
(In reply to Carlos Alberto Lopez Perez from comment #14)
> (In reply to Mero from comment #13)
> > (In reply to Carlos Alberto Lopez Perez from comment #12)
> > > Those binaries are intended to run inside the flatpak environment. They
> > > won't run on any other distro or outside of the flatpak environment.
> > 
> > That is what I mean too. It may be this dependency package flatpak that I
> > didn't build and it crashes the run  now. Or something else needed. I
> > disabled gobject introspection, bubblewrap, and wayland since they need new
> > headers, qemu and maybe other packages. However, cmake didn't stop the
> > minibrowser build and it is impossible to catch all these dependencies. As
> > far as I know, flatpak also may require the latest system headers to build
> > and run. I read the scripts in the github, but I suppose they are only for
> > the mac systems and cannot be applied.
> 
> Ok. I'm not sure what you are exactly trying to do but it looks to me it is
> not going to work.
> 
> I will explain briefly how to build WebKit for Linux (either WPE or
> WebKitGTK):
> 
> 1) First about the machine: You need a really beefy machine. WebKit is huge
> and complex c++ software that takes ages to build. The bare minimum you need
> is a 4-core Intel CPU with 12GB of RAM and a SSD with at last 50GB free of
> disk space. With a setup like this one it would take around 4-8 hours to
> build. If you want to do it in less than an hour then you need at least 16
> powerful cores and and 64GB of RAM.
> 
> The build system will try to use all your cores by default so you need at
> least 2GB of RAM free per vcore otherwise the compiler will be killed by the
> system or will fail with strange errors because there is not enough RAM.
> Anything less than that don't even try. Is not going to work.
> 
> 2) Then the process of building WebKitGTK is documented here:
> 
> https://trac.webkit.org/wiki/BuildingGtk
> 
> Notice the first step is running this command:
> Tools/Scripts/update-webkitgtk-libs
> 
> That will download and install the flatpak SDK that you need to continue
> developing.
> 
> That is a container that has all the required dependencies.
> 
> 
> So the stes are:
> 
> 1. Get the flatpak SDK
> $ Tools/Scripts/update-webkitgtk-libs
> 
> 2. Build WebKit
> $ Tools/Scripts/build-webkit --gtk
> 
> 3. Run the minibrowser:
> Tools/Scripts/run-minibrowser --gtk
> 
> 
> 
> If you want to try the WPE port just replace "--gtk" with "--wpe"
> 
> Hope it helps


That is big hindrance in building webkit. I think there is something wrong in webkit architecture. I think you agree that I can build all packages needed to webkit with a humble hardware and then finally, the most important package webkit requires such a powerful hardware and it is impossible.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230513/cf7e2c25/attachment.htm>