[Webkit-unassigned] [Bug 183595] Cmake for static build of libjavascriptcoregtk and libwebkit2gtk fails: install TARGETS given no ARCHIVE DESTINATION for static library target "WebKit".

[bugzilla-daemon at webkit.org]

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

--- Comment #7 from Adrian Perez <aperez at igalia.com> ---
Hi Stefan! Indeed it is tricky to get static builds to work (as you
have already discovered!), so I wanted to chime in to give you a couple
of possible alternatives that you may want to consider:

 * Build WebKitGTK+ as dynamic libraries, using a custom installation
   prefix, e.g. with “-DCMAKE_INSTALL_PREFIX=/usr/libexec/yelp-webkit”,
   disabling the WebKitGTK+ features that Yelp does not need to work, 
   and then linking Yelp to the libraries in the custom prefix.

 * Use something like Flatpak which is precisely intended for bundling
   applications, where application bundles can have their dependencies
   included with them. You could have a custom Flatpak build of Yelp
   for your distribution which includes a custom build of WebKitGTK+
   inside the application bundle.

Any of the above will get you out of the “build a static WebKitGTK+”
minefield. That being said, we are not against using static builds of
WebKitGTK+ but as Michael already mentioned, it is not a particularly
attractive option: static builds prevent the multiple processes that
are needed by WebKitGTK+ from sharing the code segments of the shared
libraries (which saves both disk space and memory).

-- 
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/20180313/17fe1e47/attachment.html>