I've been thinking that the only difference between client and embedding
is the list of modules and a few export issues. If we could separate the
module lists out into a separate file and sort out the export issues, it
would greatly increase the reliability of the embedding builds. The
principle reason for failure is that no one remembers to update the
embedding build.
If we could combine the makefiles before setting up a tinderbox it would
greatly increase the chances of it staying green.
Chris McAfee wrote:
> Hi Chris,
>
> I'm taking a look at what the embed guys have
> done with embed.mk and BUILD_MODULES, it still
> looks kinda hacky to me. My ultimate goal here is
> to get the build simple enough to set up an
> embed-only tinderbox.
>
> Some things that I think need to happen:
>
> * CVS module for embed project
> * probably switch to embedAll build module
> in client.mk, and then kick the hacky part
> of the build over to embed.mk. We've done
> a lot of work in client.mk and I'd hate to
> start over or copy this file.
> * Group all the weird embed config flags into
> a single embed config flag, so users don't
> have to keep this set of changes up to date.
>
> Dougt says the files needed for embed are currently
> most of SeaMonkeyAll anyways, but we need a place to
> start landing small fixes to this problem instead of
> just throwing up our hands and pulling the whole
> SeaMonkeyAll world down.
>
> If anyone else is hacking on this, or has something to
> say or warn me about, please followup here.
>
> -Chris
