Closed Bug 40013 Opened 25 years ago Closed 23 years ago

Spurious ToolServer Macintosh build dependancy

Categories

(SeaMonkey :: Build Config, defect, P3)

PowerPC
All
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 98349
mozilla0.9.6

People

(Reporter: gordon, Assigned: sdagley)

References

Details

(Whiteboard: [BUILD CONFIG])

Attachments

(7 files)

[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.
Sorry, didn't realize the first of those attachments actually went through.
Gordon (Sheridan), Simon, could you help me review this bug? Thanks. Is it possible to do without the stub library (NSStdLib) altogether?
Not without some work: NSRuntime has a recursive dependancy with NSStdLib.
Assignee: wtc → sfraser
Target Milestone: --- → M17
We can indeed remove ToolServer from the mozilla build process.
Simon, why do we need the stub library at all?
Because we need to resolve a circular dependency between NSRuntime and NSStdLib.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: M17 → ---
Move to browser component.
Component: NSPR → Build Config
Product: NSPR → Browser
Target Milestone: --- → M18
Version: 4.0 → other
Build coinfig issue, can be dealt with later.
Target Milestone: M18 → M20
adding text to whiteboard
Whiteboard: [BUILD CONFIG]
Mozilla0.9
Target Milestone: M20 → mozilla0.9
assigning to sdagley
Assignee: sfraser → sdagley
Status: ASSIGNED → NEW
*** Bug 75136 has been marked as a duplicate of this bug. ***
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
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...
Why do we need a new version of NSRuntime.mcp for Pro 5?
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.
Target Milestone: mozilla0.9 → mozilla0.9.1
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
Moving to 0.9.3.
Target Milestone: mozilla0.9.2 → mozilla0.9.3
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
Target Milestone: mozilla0.9.4 → mozilla0.9.5
This will finally go away once we move to a CW Pro 7 based build
Target Milestone: mozilla0.9.5 → mozilla0.9.6
Blocks: 98349
No longer blocks: 98349
*** This bug has been marked as a duplicate of 98349 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: