On 03/07/08 08:44, Luca Olivetti wrote: > En/na Klaus Schmidinger ha escrit: >> On 03/06/08 20:37, Ville Skyttä wrote: >>> Hello, >>> >>> The attached patch makes VDR's Makefile use pkgconfig for finding libs and >>> include dirs of freetype and fontconfig instead of making assumptions. >> How about putting that stuff at the same place everywhere? >> Why must it have to be somewhere else on every system? > > If you use packages provided by your linux distribution, usually include > files are in /usr/include and libraries are in /usr/lib, while if you > compile the source tarball yourself they go in /usr/local/include and > /usr/local/lib or wherever you decide to put them (if, e.g., you're > trying another version while you're keeping the old one, though I don't > know if pkg-config will handle this case) The root of the whole problem here IMHO is freetype2's weird way of handling its include files. I never understood why they had to use these strange macros for the includes. An application using freetype2 shouldn't have to add -I/usr/include/freetype2 to its include path. It should be possible to do #include <freetype2.h> and the rest should be handled inside that file. No weird macros, no extra include paths. BTW: whether an include file is in /usr/include or /usr/local/include doesn't matter - it is already found in both cases, without any extra effort. And the one in /usr/local/include takes precedence, just as one would ecpect. Klaus _______________________________________________ vdr mailing list vdr@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
