Hello,
I'm new to this list and I've joined after my discovery of the new Chromium
WebKit API. Great work, it's awesome.
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 ?
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 ?
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 ?
--
Thanks,
Balaji
--
Chromium Developers mailing list: [email protected]
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
