302363 - Process and use auto-generated nsStaticComponents.cpp

Status: RESOLVED INCOMPLETE

(Camino Graveyard :: General, defect)

Description

[Mark Mentovai]

Currently, static Camino builds use their own static (heh) static component list
from camino/src/application/nsStaticComponents.cpp.  All of its lizard cousins
use dynamic (heh) static component lists automatically generated as a result of
how things were configured.

During the xpfe portion of a static Camino build, an nsStaticComponents.cpp is
generated for Mozilla.app.  It's unusable as-is for Camino's purposes, but it
should be possible to either transform this file or generate a fresh one
suitable for Camino.

Comment 1

[Samuel Sidler (old account; do not CC)]

Mark, is this still something you're working on? Any estimate for when it'll be done? Is it something that's important or something we can push off for another year (i.e. Camino 2.0)?

Comment 2

[Mark Mentovai]

This isn't important, it's just something to make the build process a little less fragile.