What I've learned from this thread, is that AppleWin and AppleMac are the
only two ports which require lists of exported symbols.  If both were to
convert to using EXPORT decorators instead, then we could remove needs for
fixing export lists.

Please correct me if I've misunderstood.

Other ports (including GTK), it seems need an internals-specific export
macro, in order to export window.internals necessary symbols from their
WebKit dynamic library.  I believe this is true of all ports (with the
possible exception of Chromium).


On Thu, Jan 31, 2013 at 5:55 PM, Martin Robinson <mrobin...@webkit.org>wrote:

> On Thu, Jan 31, 2013 at 5:39 PM, Ryosuke Niwa <rn...@webkit.org> wrote:
> > Doesn't GTK+ port also require symbol exports for WebKit2? In
> particular, I
> > thought all symbols used in Internals need to be exported there.
>
> WebKitGTK+ does not need to export symbols from WebCore for WebKit2,
> because WebCore is built as a static convenience library. We do need
> to export symbols for the Internals library because it's built as a
> separate object that links against libwebkitgtk. Adding an export
> macro for Internals would be great for us, since we wouldn't have to
> export so many symbols via Source/autotools/symbols.filter. It would
> also decrease the maintenance burden for non-GTK+ port contributors.
>
> --Martin
> _______________________________________________
> webkit-dev mailing list
> webkit-dev@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-dev
>
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev

Reply via email to