Do not auto-detect jar manifests

VERIFIED WONTFIX

Status

SeaMonkey
Build Config
--
enhancement
VERIFIED WONTFIX
16 years ago
14 years ago

People

(Reporter: hacker formerly known as seawood@netscape.com, Assigned: hacker formerly known as seawood@netscape.com)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

So while playing around with bug 167254, I noted that invoking extra shell
processes has a signficant impact on our win32 build times.  For every Makefile
processed during the moz libs pass (~740 of them), we automatically invoke a
shell process to do a file detection test for jar.mn.  We should see if there's
a signficant speedup to be gotten by requiring directories to set JAR_MANIFEST
(or CHROME_MANIFEST) rather than attempting auto-detection.
Created attachment 98805 [details] [diff] [review]
Explicitly list JAR_MANIFEST
The speedup turned out to be virtually non-existant over the course of the build.
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WONTFIX

Comment 3

16 years ago
verified wontfix.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.