hi, after the comment in: https://bugzilla.redhat.com/show_bug.cgi?id=467416#c7 is there any reason for the fontconfig package? the only other package which require it is pango does it really need or the same rules apply to it as for cairo?
Op dinsdag 27-01-2009 om 16:24 uur [tijdzone +0100], schreef Farkas Levente:
hi, after the comment in: https://bugzilla.redhat.com/show_bug.cgi?id=467416#c7 is there any reason for the fontconfig package? the only other package which require it is pango does it really need or the same rules apply to it as for cairo?
Hi,
As with cairo, fontconfig/freetype is also an optional dependancy for Pango
Regards,
Erik van Pienbroek
Erik van Pienbroek wrote:
Op dinsdag 27-01-2009 om 16:24 uur [tijdzone +0100], schreef Farkas Levente:
hi, after the comment in: https://bugzilla.redhat.com/show_bug.cgi?id=467416#c7 is there any reason for the fontconfig package? the only other package which require it is pango does it really need or the same rules apply to it as for cairo?
Hi,
As with cairo, fontconfig/freetype is also an optional dependancy for Pango
does this means both fontconfig/freetype are usefulness in mingw32?
Op dinsdag 27-01-2009 om 17:18 uur [tijdzone +0100], schreef Farkas Levente:
Erik van Pienbroek wrote:
As with cairo, fontconfig/freetype is also an optional dependancy for Pango
does this means both fontconfig/freetype are usefulness in mingw32?
As far as I can tell, fontconfig and freetype were used at the time when there was no native Win32 font support in Pango yet. Cairo wasn't born yet at that time. A lot has changed in the last few years regarding Win32 support and I think fontconfig and freetype are kinda obsolete for Win32 environments right now.
At http://www.gtk.org/download-windows.html I saw the following comment about fontconfig and freetype:
-----
About freetype
This is used by GIMP and by Pango's pangoft2 library. For just GTK+ applications you will not need it.
About fontconfig
Fontconfig is used by the FreeType2 backend in Pango (pangoft2) and by GIMP. Contrary to what many seem to think, fontconfig is in no way dependent on X11, so it does make some sense to use it on Windows. GTK+ does not use pangoft2, so you probably will not need this unless for GIMP. This is a slightly fixed version of fontconfig 2.4.2 from the date indicated.
-----
So there are no real users of fontconfig and freetype on Win32 except for GIMP. I searched for more information about this and stumbled upon http://freetype.gimp.org/
This website has the following note:
-----
The FreeType Plug-In is not being developed further, nor is it actively maintained. We believe that the GIMP text tool has become sufficiently good so that there's not any longer a need for this plug-in.
-----
I think it is safe to forget about fontconfig and freetype on Win32 and stick with the native font implementations of Cairo and Pango.
Regards,
Erik van Pienbroek
On Thu, Jan 29, 2009 at 08:25:30PM +0100, Erik van Pienbroek wrote:
I think it is safe to forget about fontconfig and freetype on Win32 and stick with the native font implementations of Cairo and Pango.
Thanks for looking into this in detail. Do you think it's worth just keeping the packages around?
Rich.
Richard W.M. Jones wrote:
On Thu, Jan 29, 2009 at 08:25:30PM +0100, Erik van Pienbroek wrote:
I think it is safe to forget about fontconfig and freetype on Win32 and stick with the native font implementations of Cairo and Pango.
Thanks for looking into this in detail. Do you think it's worth just keeping the packages around?
i'd keep them around but don't update it.
Erik van Pienbroek wrote:
Op dinsdag 27-01-2009 om 16:24 uur [tijdzone +0100], schreef Farkas Levente:
hi, after the comment in: https://bugzilla.redhat.com/show_bug.cgi?id=467416#c7 is there any reason for the fontconfig package? the only other package which require it is pango does it really need or the same rules apply to it as for cairo?
Hi,
As with cairo, fontconfig/freetype is also an optional dependancy for Pango
but unfortunately none of these option have for pango --disable-xlib --disable-xcb --enable-win32 --disable-ft and without freetype i've got dozens of errors like this: ------------------------------------------ i686-pc-mingw32-gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/include/freetype2 -I . -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions --param=ssp-buffer-size=4 -mms-bitfields -mms-bitfields -MT harfbuzz-dump-main.o -MD -MP -MF .deps/harfbuzz-dump-main.Tpo -c -o harfbuzz-dump-main.o harfbuzz-dump-main.c In file included from harfbuzz-dump.c:27: harfbuzz-impl.h:29:22: error: ft2build.h: No such file or directory harfbuzz-impl.h:30:10: error: #include expects "FILENAME" or <FILENAME> harfbuzz-impl.h:31:10: error: #include expects "FILENAME" or <FILENAME> In file included from harfbuzz-impl.h:33, from harfbuzz-dump.c:27: harfbuzz-global.h:32:10: error: #include expects "FILENAME" or <FILENAME> ------------------------------------------ ft2build.h is in freetype package.
Op dinsdag 27-01-2009 om 18:12 uur [tijdzone +0100], schreef Farkas Levente:
but unfortunately none of these option have for pango --disable-xlib --disable-xcb --enable-win32 --disable-ft and without freetype i've got dozens of errors like this:
i686-pc-mingw32-gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/include/freetype2 -I . -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions --param=ssp-buffer-size=4 -mms-bitfields -mms-bitfields -MT harfbuzz-dump-main.o -MD -MP -MF .deps/harfbuzz-dump-main.Tpo -c -o harfbuzz-dump-main.o harfbuzz-dump-main.c In file included from harfbuzz-dump.c:27: harfbuzz-impl.h:29:22: error: ft2build.h: No such file or directory harfbuzz-impl.h:30:10: error: #include expects "FILENAME" or <FILENAME> harfbuzz-impl.h:31:10: error: #include expects "FILENAME" or <FILENAME> In file included from harfbuzz-impl.h:33, from harfbuzz-dump.c:27: harfbuzz-global.h:32:10: error: #include expects "FILENAME" or <FILENAME>
ft2build.h is in freetype package.
Hi,
This error is caused by a native copy of freetype (as the folder /usr/include/freetype2 is part of the compiler flags). This is only a problem for local builds because freetype isn't installed in a mock builroot.
The real cause is pkg-config. Even if we override the PKG_CONFIG_PATH, pkg-config also searches in %{_libdir}/pkgconfig, as can be read in the man page:
By default, pkg-config looks in the directory prefix/lib/pkgconfig for these files; it will also look in the colon-separated (on Windows, semicolon-separated) list of directories specified by the PKG_CONFIG_PATH environment variable.
I think the best way to solve this problem is by asking the pkg-config maintainer if an extra environment variable can be added (something like PKG_CONFIG_IGNORE_NATIVE=1) which ignores any files in %{_libdir}/pkgconfig
Regards,
Erik van Pienbroek
Op dinsdag 27-01-2009 om 19:37 uur [tijdzone +0100], schreef Erik van Pienbroek:
I think the best way to solve this problem is by asking the pkg-config maintainer if an extra environment variable can be added (something like PKG_CONFIG_IGNORE_NATIVE=1) which ignores any files in %{_libdir}/pkgconfig
I just created a patch which does the above. Feel free to submit it to the pkg-config maintainer.
Regards,
Erik van Pienbroek
On Tue, Jan 27, 2009 at 07:53:05PM +0100, Erik van Pienbroek wrote:
Op dinsdag 27-01-2009 om 19:37 uur [tijdzone +0100], schreef Erik van Pienbroek:
I think the best way to solve this problem is by asking the pkg-config maintainer if an extra environment variable can be added (something like PKG_CONFIG_IGNORE_NATIVE=1) which ignores any files in %{_libdir}/pkgconfig
I just created a patch which does the above. Feel free to submit it to the pkg-config maintainer.
I agree, and will submit your patch upstream.
Rich.
Richard W.M. Jones wrote:
On Tue, Jan 27, 2009 at 07:53:05PM +0100, Erik van Pienbroek wrote:
Op dinsdag 27-01-2009 om 19:37 uur [tijdzone +0100], schreef Erik van Pienbroek:
I think the best way to solve this problem is by asking the pkg-config maintainer if an extra environment variable can be added (something like PKG_CONFIG_IGNORE_NATIVE=1) which ignores any files in %{_libdir}/pkgconfig
I just created a patch which does the above. Feel free to submit it to the pkg-config maintainer.
I agree, and will submit your patch upstream.
what's more it's may be happened with other mingw32 packages too just we don't recognize it...
-
Erik van Pienbroek -
Farkas Levente -
Richard W.M. Jones