84010 - Mozilla needs a flexible scheme for linking modules together

Status: RESOLVED INCOMPLETE

(Firefox Build System :: General, defect, P3)

Description

[Adam Lock]

Modules have too much say in how they are linked together to produce runtime
libraries. 

That kind of thing should be left to the end of a build where for example a
manifest list could be used to combined the modules together into a set of
runtime libraries.

It would be desirable to do this in a way that doesn't require embedders  to
maintain a complete and seperate module manifest of their own.

Comment 1

[cls]

Windows. Bouncing to leaf.

Can you elaborate on how the modules dictate how they are linked together as
opposed to the build system dictating it?  It sounds sort of like you want the
--enable-meta-components stuff we are doing in bug 46775 but for a stock build,
I'm not seeing the problem with the current scheme.

Comment 2

[Adam Lock]

I'll briefly describe what I think is necessary for embedding.

We, or rather embedders need a way to easily pick and choose what components go
into a build. For example, one embedder may not need global history while
another wants the cut-down global history. Yet another embedder may want to put
all components into a couple of shared libs instead of the stock 70+ that we
have now. In short we need a flexible mechanism for linking Mozilla in all these
different ways.

To do this, it should be possible on Win32 and Unix to feed a manifest of the
obj/lib files produced from the build through a script that constructs the
shared libraries. Embedders who want to pick and choose what components are in
their build can tailor this manifest to their requirements.

Does this tie in with the static build work?

Comment 3

[Jon Granrose]

bug cleanup - all leaf's bugzilla bugs should be assigned to [e-mail]
(not [e-mail]), now and any future bugs created.

this should be a one time change, apologies for the spam.

Comment 4

[Chase Phillips]

Mass reassign of open bugs for [e-mail] to [e-mail].

Comment 5

[J. Paul Reed [:preed]]

Mass re-assign of bugs that aren't on the build team radar, so bugs assigned to [e-mail] reflects reality.

If there is a bug you really think we need to be looking at, please *email* [e-mail] with a bug number and explanation.

Comment 6

[Chris Cooper [:coop] (he/him)]

Mass bug cleanup for Core:Build Config.

If you feel this bug has been closed in error, please re-open with new details.