From: Sebastian Spaeth <Sebastian@SSpaeth.de> - 2001-02-12 19:57:27
the embedded build now uses embed.jar from today on which contains the
chrome, here the
original message from Adam Lock:
> Adam Lock wrote:
> >I've changed mozilla/embedding/config so that the chrome for the
> >embedding builds is created from embed-jar.mn manifest file and placed
> >into embed.jar.
> > The installed-chrome.txt file has also been updated so
> > that winEmbed and gtkEmbed will automatically look in this file for all
> > their chrome.
> Sorry for not having checked before posting this, but does it include
> mfcEmbed as well? Or do not all embedding codes have to be updated
We have used winEmbed on Win32 and gtkEmbed on Linux up until now as our
smoketest apps but mfcEmbed may be used in future. When that happens it
replace winEmbed in the nightlies.
If you want to try out mfcEmbed right now with the embed.jar file, do
nmake /f client.mak build_all (as you would for a normal client build)
nmake /f makefile.win
This will create a new $(DIST)/Embed directory containing the subset of
Mozilla libs and chrome needed for our smoketest applications. Copy and
mfcEmbed from here and it should pick up same settings as winEmbed. The
applies for the ActiveX control - copy mozctl.dll there (to fix up the
settings or use mozctlx.dll) and that should also work.
Currently $(DIST)/Embed zips up to about 2.8Mb on Win32 and 5Mb on
The lists of what gets installed into this directory are listed in
mozilla/embedding/config/basebrowser-win, basebrowser-unix and
Other embedding projects can always modify these lists if they have
files to install.