I built Firefox 2.0.0.13 trunk and created an embedding package with out any client.win files. I'm using MSVC 6 and Feb 2003 PSDK as per the build documentation. Following is my .mozconfig file for this build. . $topsrcdir/browser/config/mozconfig mk_add_options [EMAIL PROTECTED]@/ff-dbgac_add_options --disable-tests ac_add_options --disable-optimizeac_add_options --enable-debug The embedding package process didn't generate .manifest file for the embed.jar. Hence I created one as follows: (When I ran the embed packaging build, I only got embed.jar but not embed.manifest file. I found out from Firefox 2.0 build and a crash in gklayout.dll that .manifest for chrome is necessary. )
skin global embed/1.0 jar:embed.jar!/skin/classic/global/locale pipnss en-US jar:embed.jar!/locale/en-US/pipnss/locale global en-US jar:embed.jar!/locale/en-US/global/locale necko en-US jar:embed.jar!/locale/en-US/necko/content global jar:embed.jar!/content/global/content xbl-marquee jar:embed!/content/xbl-marquee/ My question, does the above .manifest cover all the chrome entries in the standard embed.jar file? Am I missing anything here? Also, Is there a configuration to make this .manifest generation automatic from the "embed packaging" process? Thanks, Babu. _________________________________________________________________ Going green? See the top 12 foods to eat organic. http://green.msn.com/galleries/photos/photos.aspx?gid=164&ocid=T003MSN51N1653A _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
