Bug 20623 - WebCore's JS Bindings should be built as part of a separate phase/target/project
Summary: WebCore's JS Bindings should be built as part of a separate phase/target/project
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 20619
  Show dependency tree / graph
 
Reported: 2008-09-03 04:33 PDT by Eric Seidel (no email)
Modified: 2010-04-21 12:59 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Seidel (no email) 2008-09-03 04:33:35 PDT 
WebCore's JS Bindings should be built as part of a separate phase/target/project

In order to more easily support KJS vs. V8 bindings (w/o having two copies of a single XCode project), WebCore should break out the build of bindings into a separate phase or target or project.  Target is probably the easiest way to start.  Then we'd have 4 targets in WebCore:

WebCore (core)
WebCore (JSC bindings)
WebCore (v8 bindings)
WebCore (library)

Obviously we could come up with nicer names than those.
Comment 1 Eric Seidel (no email) 2010-04-21 12:59:37 PDT 
This would still be nice to do, but I'll close this for now.