Guys, I've followed on the great work of Ben and others on *embedding mozilla* issues, gecko profile, libxul and related stuff. They are really making the embedding process easier, and of course I particularly agree with this kind of initiative.
But over my point of view, although things keep getting better and better they're not yet ideal. In my case, for example, I'm working on a mozilla-based embedded browser for the nokia 770 linux-running target, and I'm not completely *pleased* with the current footprint of shared build of xulrunner that I am using for embedding mozilla. Even using the current 'minimal' gecko profile, the footprint a *bit* large. On the other hand, I've spent part of my free time to help dougt out with some minimo stuff (mozilla.org/proejcts/minimo) on linux, and the 11Mbs of footprint that I got would be better for my needs. The problem is : minimo builds only statically (once it's not following the libxul linking strategy for shared builds so far), hence most of '.a' libs are linked against the minimo executable itself. So, I'm wondering what do I have to do to put my browser running over a static build ? Is it feasible linking things/libs against a single lib (just as libxul) ? How to reach this ? (please, don't get me wrong here, I'm not complaining at all and keep up the great work). -- --Antonio Gomes _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
