Bug 20623
| Summary: | WebCore's JS Bindings should be built as part of a separate phase/target/project | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | mrowe |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Mac | ||
| OS: | OS X 10.5 | ||
| Bug Depends on: | |||
| Bug Blocks: | 20619 | ||
Eric Seidel (no email)
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Eric Seidel (no email)
This would still be nice to do, but I'll close this for now.