Closed
Bug 40013
Opened 25 years ago
Closed 23 years ago
Spurious ToolServer Macintosh build dependancy
Categories
(SeaMonkey :: Build Config, defect, P3)
Tracking
(Not tracked)
mozilla0.9.6
People
(Reporter: gordon, Assigned: sdagley)
References
Details
(Whiteboard: [BUILD CONFIG])
Attachments
(7 files)
260.94 KB,
application/octet-stream
|
Details | |
22.51 KB,
application/octet-stream
|
Details | |
30.72 KB,
application/octet-stream
|
Details | |
22.54 KB,
application/octet-stream
|
Details | |
25.82 KB,
application/octet-stream
|
Details | |
18.08 KB,
application/octet-stream
|
Details | |
20.57 KB,
application/octet-stream
|
Details |
[Low-hanging fruit for someone who was annoyed by the build process.]
ToolServer is currently only being used to build NSPR stub libraries, although
CodeWarrior 5, at least, is fully capable of making those on its own. It appears that
the only stub library being built is NSStdLib. I was able to modify the
:lib:mac:NSStdLib:NSStdLib.mcp[Stubs] target to use CW's built-in facilities. There's
another RunTSScript target, :lib:mac:NSRuntime:NSRuntime.mcp[Stubs], but it doesn't
appear to get built. I also updated that for CW, though, so that the project can load
without error. Doing these two tasks, I was able to disable (compress) ToolServer,
MPW, and the RunTSScript "compiler" and then successfully built a working
MozillaDebug.
Although I didn't change any source files, there are 4 ToolServer scripts which can be
removed from the repository if these projects are checked in. The existance of these
files is benign, but they're unnecessary. They are :lib:mac:NSRuntime:NSRuntime.mcp,
:lib:mac:MacMemoryAllocator:MemAllocator.exp_MakeStubs and
:MemAllocator.exp_TS, and :lib:mac:NSStdLib:NSStdLib:NSStdLib.exp_TS.
Reporter | ||
Comment 1•25 years ago
|
||
Reporter | ||
Comment 2•25 years ago
|
||
Reporter | ||
Comment 3•25 years ago
|
||
Reporter | ||
Comment 4•25 years ago
|
||
Sorry, didn't realize the first of those attachments actually went through.
Comment 5•25 years ago
|
||
Gordon (Sheridan), Simon, could you help me
review this bug? Thanks.
Is it possible to do without the stub library
(NSStdLib) altogether?
Reporter | ||
Comment 6•25 years ago
|
||
Not without some work: NSRuntime has a recursive dependancy with NSStdLib.
Updated•25 years ago
|
Assignee: wtc → sfraser
Target Milestone: --- → M17
Comment 7•25 years ago
|
||
We can indeed remove ToolServer from the mozilla build process.
Comment 8•25 years ago
|
||
Simon, why do we need the stub library at all?
Comment 9•25 years ago
|
||
Because we need to resolve a circular dependency between NSRuntime and NSStdLib.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Updated•24 years ago
|
Target Milestone: M17 → ---
Comment 10•24 years ago
|
||
Move to browser component.
Component: NSPR → Build Config
Product: NSPR → Browser
Target Milestone: --- → M18
Version: 4.0 → other
Comment 15•24 years ago
|
||
*** Bug 75136 has been marked as a duplicate of this bug. ***
Comment 16•24 years ago
|
||
Transferring blocks from duplicate bug.
This blocks us from building in CodeWarrior 6 on Mac OS X.
I'll test the attached file tonight and see if it works. If so, I suggest we get
this in ASAP.
Blocks: 53682
Comment 17•24 years ago
|
||
Looking good. I'll attach updated versions of NSRuntime and NSStdLib based off of
the April 08 2001 trees.
I've even done CodeWarrior 5 and 6 versions, though the 5 is all that will need
to be checked in. Can we *please* do this before all this work bit rots?
Gordon's other comments about removing dead files still apply.
Thanks for this one...
Comment 18•24 years ago
|
||
Comment 19•24 years ago
|
||
Comment 20•24 years ago
|
||
Comment 21•24 years ago
|
||
Comment 22•24 years ago
|
||
Why do we need a new version of NSRuntime.mcp for Pro 5?
Comment 23•24 years ago
|
||
I updated the Stubs target in NSRuntime so it would actually build the Stub
library for NSRuntime correctly. If this truly obsolete then its presumably
better to just delete the Stubs target altogether from NSRuntime.mcp.
Assignee | ||
Updated•24 years ago
|
Target Milestone: mozilla0.9 → mozilla0.9.1
Comment 24•24 years ago
|
||
Setting target milestone to 0.9.2 (check it in anytime, even before, when the
tree is open for). Per PDT triage.
Target Milestone: mozilla0.9.1 → mozilla0.9.2
Comment 26•23 years ago
|
||
Doesn't look like this is getting fixed before the freeze tonight.
Pushing out a milestone. Please correct if I'm mistaken.
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla0.9.4 → mozilla0.9.5
Assignee | ||
Comment 27•23 years ago
|
||
This will finally go away once we move to a CW Pro 7 based build
Target Milestone: mozilla0.9.5 → mozilla0.9.6
Comment 28•23 years ago
|
||
*** This bug has been marked as a duplicate of 98349 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•