We need the ablity to build the base embedding requirements from the mozilla tree without having to build unneeded components such as seamonkey specific bits, mailnews, ect.
I checked in a embed.mk files to the root level of mozilla. This will build just what is required by gtkEmbed. Next step is for leaf to build gtkEmbed using this makefile instead of the client.mk files. Leaf, I am assigning this bug to you. after doing your morning verification builds, could you do a clobber_all then build gtkEmbed against this makefile?
Assignee: dougt → leaf
that's a negative, poppa bear. We need to keep the built tree around in case we need to do depend build respins. We *could* do something along the lines of producing an embedding build at an odd hour with a separate at job, though. Thereby not requiring a separate build machine for embedding release stuff. Unless, of course, you need builds done in a time-critical fashion, in which case, we're going to need another release machine for embedding. Feedback welcome.
These builds are not time critical (now). Can you spin these builds before you spin Seamonkey? If equipment is a problem, let me know.
I could swear this is a dup of another bug to set up standalone embedding builds, but I can't seem to find it. marking future for now.
Target Milestone: --- → Future
*** Bug 62657 has been marked as a duplicate of this bug. ***
Summary: Need to be able to build "embedding" seperately from seamonkey → Need to be able to build "embedding" separately from seamonkey
Fixed by xulrunner.
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.