Re: [ft-devel] Slightly modified header inclusion scheme

[Behdad Esfahbod]

On 15-06-22 03:44 PM, Werner LEMBERG wrote:
> 
>> This is extremely problematic.  Please read my original report that
>> caused the first header file layout change:
>>
>>   http://comments.gmane.org/gmane.comp.fonts.freetype.devel/9052
> 
> OK, but there's a fundamental difference: freetype.pc now has a
> *single* -I directive (e.g. -I/usr/include),

That's the problem.  Why exactly that is not desired is a bit complicated to
explain.  Suffice to say that this makes it extremely hard to use custom
versions of other modules that put their headers directly in /usr/include.

To make the problem worse, pkg-config by default removes -I/usr/include from
CFLAGS, making this problem disappear until one is cross-compiling or
otherwise is not using /usr as their prefix.

Instead, if FreeType uses a private include space, ie. /usr/include/freetype2,
there's no chance that the -I introduced by FreeType will affect header
inclusion order of other modules.

Does this make sense?

b


> namely to find
> `ft2build.h'.  The other header files are `hidden'.
> 
>> If you are changing this again, can you please just under the
>> simplification that you did in that old thread?  Ie, make everything
>> look like it used to before 2013, except that ft2build.h will be
>> inside freetype2/ as opposed to outside it as it was pre-2013.
> 
> I've re-read your comments in the above thread, and I think they don't
> apply – but maybe I'm missing something...
> 
> 
>     Werner
>