<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK OSX] libGObjectDOMBindings.a is not linked into libwebkit2gtk-4.0.37.dylib"
href="https://bugs.webkit.org/show_bug.cgi?id=153117#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK OSX] libGObjectDOMBindings.a is not linked into libwebkit2gtk-4.0.37.dylib"
href="https://bugs.webkit.org/show_bug.cgi?id=153117">bug 153117</a>
from <span class="vcard"><a class="email" href="mailto:jeremyhu@apple.com" title="Jeremy Huddleston Sequoia <jeremyhu@apple.com>"> <span class="fn">Jeremy Huddleston Sequoia</span></a>
</span></b>
<pre><span class="quote">> Should this be -Wl,-all_load ${library} -Wl,-no-all_load</span >
No.
<span class="quote">> or does it not work the same as --whole-archive?</span >
It does not. There is nothing exactly analogous. There are two similar options in ld64:
-all_load
Loads all members of static archive libraries.
-force_load path_to_archive
Loads all members of the specified static archive library. Note: -all_load forces all members
of all archives to be loaded. This option allows you to target a specific archive.
-force_load would be ideal if we had a contract that the arguments to the macro were always static archives that we built for inclusion in the library. I tried that first, and it didn't work because the macro is called with arguments other than just static archives that we had built. -all_load is thus the ideal choice, and it's also used elsewhere in the build already.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>