Benjamin made seamonkey pull toolkit and chrome. The change makes standalone modules like xpcom or transformiix standalone pull those, too. Which it shouldn't.
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
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.
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.
No longer SeaMonkey but Core, but I think this must be won't fix now?
Component: Build Config → Build Config
Product: SeaMonkey → Core
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.