Closed
Bug 469171
Opened 17 years ago
Closed 15 years ago
SpiderMonkey should do two-stage build
Categories
(Firefox Build System :: General, defect)
Firefox Build System
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jimb, Unassigned)
Details
We would like to be able to use the SpiderMonkey shell in the SpiderMonkey build process. We would like to be able to assemble special-purpose bytecode, generate boilerplate functions, and so on, using JavaScript as our scripting language.
This entails using two passes. We would build the first pass with various features disabled, to produce a shell that we can use in the second pass.
Probably this means creating a subdirectory of js/src for each pass, whose makefile includes the important stuff from some js/src/ .mk file, uses VPATH to find the sources in js/src, as they are now, and builds SpiderMonkey and the shell with appropriate options.
Comment 1•17 years ago
|
||
To summarize a bit of conversation in #jsapi: the goal is to build a host jsshell, not threadsafe, and use that in the build process for the target jsshell. We discussed briefly whether to use the traditional host+target build system support that we already have in place, or whether to use an entire separate objdir which can be configured for the host.
| Reporter | ||
Comment 2•15 years ago
|
||
This is fixed by bug 563728.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•