[Webkit-unassigned] [Bug 27551] New: Make it possible to build JavaScriptCore as shared library without symbol lists

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=27551

           Summary: Make it possible to build JavaScriptCore as shared
                    library without symbol lists
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Mac OS X 10.5
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Platform
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: hausmann at webkit.org
                CC: kenneth.christiansen at openbossa.org



Simon Hausmann <hausmann at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #33277|                            |review?
               Flag|                            |


Created an attachment (id=33277)
 --> (https://bugs.webkit.org/attachment.cgi?id=33277)
Patch to make it possible to build JavaScriptCore as shared library on Linux
without symbol files.

Currently JavaScriptCore is built as shared library on the Apple Windows and
Mac OS X builds.

The symbols used by WebCore and WebKit are exported in JavaScriptCore via
separate files, one for MSVC and one for Mac OS X gcc. The files contain the
mangled symbol names.

It is cumbersome to maintain these lists and it becomes worse when taking
additional compilers into account, like for example g++ on Linux or RVCT for
ARM. When a new symbol needs to be exported it is necessary to determine their
mangled name for each supported compiler.

This bug tries to track the patches/work needed to replace the separately
maintained export lists with the commonly used export macros.


The initial patch merely adds the export macros where necessary and tweaks the
Visual studio and Xcode based builds to accept them, while keeping the symbol
files in place.


Pending approval for the first patch, the second step is to change the Visual
Studio and Xcode builds to fully utilize the macros and delete the symbol
files. On Windows this step will require the placement of additional export
macros that are not part of the first patch.

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