On Mon, Mar 02, 2009 at 11:21:04AM -0800, Dan Nicholson wrote: > On Mon, Mar 2, 2009 at 10:05 AM, Ken Moffat <[email protected]> wrote: > > > > Yes. So, it is desirable for xulrunner, irrelevant to firefox when > > that is built on xulrunner, and desirable for standalone firefox. > > > > Otherwise, they will build the included libmozlibpixman.a and > > libmozcairo.a. > > Right. Just for reference, the benefit of using the internal > cairo/pixman is that mozilla does extensive testing and bug fixing on > cairo since it's used on all their platforms. They'll usually > stabilize on a specific version of each so that they can deploy a > known good solution. You can see in gfx/cairo (I think that's the > path) that there are a bunch of patches they use on cairo to try to > get the best experience. Most of the patches get back upstream > (Vladimir Vukicevic from mozilla is part of the cairo dev team), but > some might not be "upstreamable." > > That's the reason why --enable-system-cairo is not the default. > Thanks for that, Dan. As someone who is known to have a low regard for the mess that is mozilla (even though it is a lot better than it used to be, e.g. ff3 even builds on ppc with the included nss/nspr) I prefer to go with what the main distros do.
ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-book FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
