On Fri, Dec 18, 2009 at 10:32 AM, Balaji Rao <[email protected]> wrote:
> I'm new to this list and I've joined after my discovery of the new Chromium
> WebKit API. Great work, it's awesome.
It's very new, so don't expect it to all quite work yet.
> I tried to compile a really stupid implementation (on Linux) with
> libWebKit.a, and it failed with a few thousand unresolved symbols. Using
> data from objdump, I figured out that functions annotated with WEBKIT_API
> were those in the list, which I figured out were due to '-fvisibility=false'
> being used for the static library case. Now I thought #defining WEBKIT_API
> to __attribute__ ((visibility("default"))) would help, but it didn't. I
> guess the encapsulating class needs to be annotated WEBKIT_API as well ? Can
> anyone please help me solve this ?
Something's confused here.
1) .a files are just archives of .o files, while visibility=hidden
only affects visibility beyond module boundaries.
2) -fvisibility=false doesn't exist, I assume you mean hidden (?)
> Also, I read somewhere in the webkit repo that gyp didn't support
> "shared_library" targets yet. Is it still true ? If yes, when can it be
> expected ?
gyp does support shared_library targets. Where did you read that?
> Obviously, the thing that would help me most is a sample implementation -
> which I think could exist because that there must have been an
> implementation that was grown parallel to the API itself. Is it the
> DumpRender tree ? Or the test-shell ? Can anyone please tell me where can I
> find one ?
test_shell:
http://src.chromium.org/cgi-bin/gitweb.cgi?p=chromium.git;a=tree;f=webkit/tools/test_shell;h=d8c06ce190f8b2facf92162a690a647984e80c10;hb=HEAD
--
Chromium Developers mailing list: [email protected]
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
