[Webkit-unassigned] [Bug 23083] New: WebKit.lib doesn't export kJSClassDefinitionEmpty

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jan 2 16:20:48 PST 2009


           Summary: WebKit.lib doesn't export kJSClassDefinitionEmpty
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Windows Vista
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebKit API
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: mculpepper at appcelerator.org

If trying to use kJSClassDefinitionEmpty for creating a new JS Class
definition, you will get a linking error in win32 if you try linking against
just WebKit.lib. Linking to both JavaScriptCore.lib and WebKit.lib solves the
problem, but there are multiple duplicate symbol definitions (since WebKit
re-exports symbols from JavaScriptCore). The easiest fix I see is to just
expose kJSClassDefinitionEmpty in the WebKit.def.. I'm attaching a patch that
does just that.

(Note: you can also solve this issue by NOT exporting any JS functions from
WebKit.lib and then link against both WebKit.lib, and JavaScriptCore.lib)

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list