On Sun, Mar 01, 2009 at 07:43:42PM -0800, Dan Nicholson wrote: > On Sun, Mar 1, 2009 at 4:10 PM, Ken Moffat <[email protected]> wrote: > > On Sun, Mar 01, 2009 at 04:59:44PM -0600, Randy McMurchy wrote: > >> Ken Moffat wrote these words on 03/01/09 16:44 CST: > >> > On Sun, Mar 01, 2009 at 03:00:39PM -0600, Randy McMurchy wrote: > >> >> Because if it still does, cairo *will* be installed and there's no > >> >> need to even have this option to comment/uncomment. > >> > > >> > That I don't understand. From one of my builds yesterday, using > >> > /opt so I could build ff3 on xulrunner (if you try that, be aware that > >> > xulrunner *will* update /etc/gre.d with a version of > >> > 1.9.0.6.system.conf which might prevent the ff3 in /usr/bin from > >> > starting - backups are useful!) using --enable-system-cairo : > >> > >> You lost me. I'll admit I'm not yet familiar with the FF3 build, but > >> my question is this: > >> > >> Does it still use Gtk+ for rendering? If so, then Gtk+ will be > >> installed on the system and therefore cairo will also be installed > >> on the system. Why don't we just default to use the system-installed > >> copy of cairo? > >> > > That's what I'm trying to do. Like all mozilla products, this is > > poorly documented - google used to know about an arch page that > > listed the config options, but they seem to have moved to using > > icecat which might not have the same defaults. > > It uses both gtk2 and cairo, just like firefox-2.x. The widget toolkit > is gtk2, but any graphics rendering it does on its own is via cairo. > Here's the key sections of configure: > > _PLATFORM_DEFAULT_TOOLKIT=cairo-gtk2 > ... > cairo-gtk2|cairo-gtk2-x11) > MOZ_WIDGET_TOOLKIT=gtk2 > MOZ_GFX_TOOLKIT=cairo > MOZ_ENABLE_GTK2=1 > MOZ_ENABLE_XREMOTE=1 > > AC_DEFINE(MOZ_X11) > MOZ_X11=1 > > TK_CFLAGS='$(MOZ_GTK2_CFLAGS)' > TK_LIBS='$(MOZ_GTK2_LIBS)' > AC_DEFINE(MOZ_WIDGET_GTK2) > ;; > > > OK, I've looked at firefox, and even with '#define MOZ_TREE_CAIRO > > 1' it seems to be using the system version. > > If firefox is using xulrunner, then it just relies on that for all the > mozilla APIs, including graphics. That's the major reason for > xulrunner. So, if you built xulrunner to use the system cairo, then > that's also what firefox will use. > > -- > Dan > --
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. ĸ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
