[EMAIL PROTECTED] wrote: > The build does not complain about xulrunner directoy missing. I'm > currently building using the following .mozconfig file (obtained from > ubrowser), with some modifications (--enable-static and --disable- > libxul).
Why are you making these modifications? Static builds are not embeddable. > I'm building a special purpose application where I only need the > rendering engine and http(s) protocol support. I don't need plugin or > extension support. I would also replace the cookie handling - > implement cookie managment myself. Can you please suggest me a > good .mozconfig options to achieve that? I strongly discourage you making changes. See http://benjamin.smedbergs.us/blog/2005-07-29/the-testing-matrix/ for my reasoning. Disabling these feature will not signficantly affect the performance or download weight of your application, but it could cause unexpected failure modes. You have a long list of configure options below. I strongly suggest you remove all of them, and just do "--enable-application=xulrunner" for a release build and "--enable-application=xulrunner --enable-debug --disable-optimize" for debugging. The more options you specify, the more likely you are to get something wrong. The only other option you really might need is --disable-javaxpcom if you don't have a JDK installed. > ac_add_options --enable-static > ac_add_options --disable-libxul You do not want these options. Libxul is faster and better to embed than other build flavors. > ac_add_options --disable-profilelocking Not recommended. --BDS _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
