<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:mcatanzaro@igalia.com" title="Michael Catanzaro <mcatanzaro@igalia.com>"> <span class="fn">Michael Catanzaro</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - [CMake][GTK][OSX] ThreadIdentifierData::initialize assertion fails because there are two copies of WTF in process (one as part of webkit2, one as part of jsc)"
href="https://bugs.webkit.org/show_bug.cgi?id=153176">bug 153176</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>achristensen@apple.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CMake][GTK][OSX] ThreadIdentifierData::initialize assertion fails because there are two copies of WTF in process (one as part of webkit2, one as part of jsc)"
href="https://bugs.webkit.org/show_bug.cgi?id=153176#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CMake][GTK][OSX] ThreadIdentifierData::initialize assertion fails because there are two copies of WTF in process (one as part of webkit2, one as part of jsc)"
href="https://bugs.webkit.org/show_bug.cgi?id=153176">bug 153176</a>
from <span class="vcard"><a class="email" href="mailto:mcatanzaro@igalia.com" title="Michael Catanzaro <mcatanzaro@igalia.com>"> <span class="fn">Michael Catanzaro</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=153176#c9">comment #9</a>)
<span class="quote">> It looks like this goes well beyond just WTF. Most of the executables are
> linking against both the dylibs and static archives. For example
> MiniBrowser is linking
>
> libwebkit2gtk-4.0.37.13.0.dylib
> libjavascriptcoregtk-4.0.18.3.2.dylib
> libbmalloc.a
> libWebCoreGTK.a
> libANGLESupport.a
> libGObjectDOMBindings.a
> libWebCorePlatformGTK.a
> libWTFGTK.a
>
> Why does cmake not realize that the functionality provided by those static
> archives is already rolled into the dylibs that it built? Depending on
> JavaScriptCore should just result in linking that dylib, not linking that
> dylib *AND* all the static archives that went into that dylib.
>
> Have I mentioned how much I dislike cmake?</span >
Clearly we need to figure out what's up here. The static libraries are "convenience libs" which are never installed: they're only there to make reasoning about the build system easier, and so that we can catch layering violations between the libraries. MiniBrowser should only be linking to libwebkit2gtk-4.0.37.13.0.dylib and libjavascriptcoregtk-4.0.18.3.2.dylib.
I wonder if the Mac port is having any similar linking problems?</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>