On 2/17/19 9:46 PM, Thanos Baloukas via blfs-dev wrote:
On 17/2/19 10:03 μ.μ., Bruce Dubbs via blfs-dev wrote:
On 2/17/19 1:38 PM, Pierre Labastie via blfs-dev wrote:
Not sure I understand: if a dep is in the recommended chain, what
does it
bring to put it in optional? Specially in this case, harfbuzz is
useless for
cairo without freetype and fontconfig... And freetype needs cairo. I
think
what I have put in the book at rev 21189 allows preventing the issue
you had.
Of course, it would not the same, for example, if a dep were
required, and
also in the recommended dependency chain... Then it would have to be
mentioned
as required.
package pango
Recommended cairo (but needs harfbuzz first)
package cairo
Required pixman and libpng only
No mention of harfbuzz
harfbuzz X
Optional cairo
If you build the optional cairo before harfbuzz, you can't build
pango until cairo is rebuilt.
The following sequence
freetype
fontconfig
cairo
harfbuzz
freetype #Rebuild with Harfbuzz support
pango
works for me. Pango builds without the need to rebuild cairo
after harfbuzz.
Actually, according to README in cairo, one font backend is required,
and the only one available for linux is fontconfig+freetype2:
===============
Font backends (required to have at least one)
---------------------------------------------
freetype font backend
---------------------
freetype >= 2.1.9 http://freetype.org
fontconfig http://fontconfig.org
quartz-font backend
-------------------
MacOS X >= 10.4 with Xcode >= 2.4
win32 font backend
------------------
Microsoft Windows 2000 or newer
================
So I think we should *require* fontconfig+freetype for cairo. And that
seems to match Thanos build order
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
