Closed
Bug 253270
Opened 20 years ago
Closed 15 years ago
standalone modules (xpcom, transformiix) should not pull toolkit or chrome
Categories
(Firefox Build System :: General, defect)
Firefox Build System
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: axel, Unassigned)
Details
Attachments
(1 file, 1 obsolete file)
1.89 KB,
patch
|
Details | Diff | Splinter Review |
Benjamin made seamonkey pull toolkit and chrome. The change makes standalone modules like xpcom or transformiix standalone pull those, too. Which it shouldn't.
Comment 1•20 years ago
|
||
bryner did it, not me. I agree XPCOM standalone shouldn't pull toolkit/, I am less sure about transformiix standalone. In particular, how does standalone transformiix get its localized strings without a chrome registry?
Assignee: bsmedberg → bryner
Reporter | ||
Comment 2•20 years ago
|
||
standalone transformiix only depends on xpcom/nspr, nothing else. And this requirement is hardcoded in modules.mk, as the scripts generating those deps catch the module dependencies, not the ones of standalone.
Comment 3•20 years ago
|
||
Reporter | ||
Comment 4•20 years ago
|
||
New patch, attachement 156051 didn't work. The checkout lines use CHECKOUT_MOZTOOLKIT instead of CVSCO_MOZTOOLKIT, so I changed that.
Reporter | ||
Updated•20 years ago
|
Attachment #156051 -
Attachment is obsolete: true
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•18 years ago
|
Assignee: bryner → nobody
Comment 5•15 years ago
|
||
No longer SeaMonkey but Core, but I think this must be won't fix now?
Product: SeaMonkey → Core
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
Updated•6 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•