14217 - run RegXPCOM to create Component Registry

Status: RESOLVED FIXED

(SeaMonkey :: Build Config, defect, P3)

Description

[Chris Yeh]

JJ:

After an optimized build is completed, you need to run the RegXPCOM application
in the main client directory. Running this tool creates a Component Registry that
needs to be shipped.

You need to run this tool twice: once in the Mozilla build for packaging in the
mozilla build.

Once in the commercial tree to ship with the commercial build.

You also need to remove the RegXPCOM and the symbol table out of the client
delivery before you deliver.

Comment 1

[J.J. Enser]

Build automation script (BuildCentral) has been updated to run RegXPCOM before
packaging, for both mozilla & seammonkey builds.

The utility (1.1MB) gets deleted after execution

Comment 2

[Simon Fraser [no longer active]]

It should not be that big. You need to turn off 'Merge into output' for the
shared libs that it links with.

Comment 3

[Suresh Duddi (gone)]

JJ are you clear on how to fix this. If not reassign to me and I will drive this
to completion.

Comment 4

[J.J. Enser]

Does it _really_ matter to have a small or large output, knowing that it gets

deleted immediately after execution ?

Right now it works fine, so I suggest to live it as is. there are zillions of

more important issues that I'd rather focus on, 2 days away from my vacation :-)



If someone decides however to update the mac project file, he/she should be aware

that the verification build script relies on it to deliver the daily bits... no

breakage allowed!