Hey, good catch! In addition to --enable-system-cairo, it looks like
there's a --enable-default-toolkit target called cairo-gtk2 which
seems intriguing for what we're doing now that gtk2 needs cairo
anyway. It sets MOZ_GFX_TOOLKIT=cairo instead of MOZ_WIDGET_TOOLKIT
which =gtk2. It looks like this changes the font handling by not
setting MOZ_ENABLE_COREXFONTS like the gtk2 target does. Not sure
what happens with that, though.
Needs some more investigation, but I'm gonna try with:
--enable-default-toolkit=cairo-gtk2
I believe this switch is for the future development of firefox, where cairo does the rendering of everything. It's still very buggy and slow though.
-- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
