standalone modules (xpcom, transformiix) should not pull toolkit or chrome

RESOLVED INVALID

Status

RESOLVED INVALID
14 years ago
6 months ago

People

(Reporter: axel, Unassigned)

Tracking

Trunk

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Reporter)

Description

14 years ago
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

14 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

14 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.
(Reporter)

Comment 4

14 years ago
Created attachment 156165 [details] [diff] [review]
use CHECKOUT_ instead of CVSCO_

New patch, attachement 156051 didn't work.
The checkout lines use CHECKOUT_MOZTOOLKIT instead of CVSCO_MOZTOOLKIT, so I 
changed that.
(Reporter)

Updated

14 years ago
Attachment #156051 - Attachment is obsolete: true
Product: Browser → Seamonkey
Assignee: bryner → nobody
No longer SeaMonkey but Core, but I think this must be won't fix now?
Component: Build Config → Build Config
Product: SeaMonkey → Core

Updated

9 years ago
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID

Updated

6 months ago
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.