[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ft-devel] Cleaning up include paths
From: |
Behdad Esfahbod |
Subject: |
Re: [ft-devel] Cleaning up include paths |
Date: |
Mon, 25 Nov 2013 17:24:35 -0500 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 |
On 13-11-25 05:21 PM, Werner LEMBERG wrote:
>>> This large patch changes the header file directory layout from
>>> `include/freetype/...' to `include/...', effectively removing
>>
>> This is actually more problematic. :( Basically you have undone what
>> I was suggesting. What I was suggesting was to move ft2build.h out
>> of /usr/include exactly so all freetype headers will be in a
>> freetype-private include dir (/usr/include/freetype2). It's the
>> "private" part in that sentence that is key. It would make sure
>> that freetype headers will be picked up exactly from where the
>> pkg-config file says, not from whatever prefix happens to be first
>> in the header search order. Does it make sense?
>
> Yes, it does, and fortunately, my announcement was written
> imprecisely, since it referred to the layout in the FreeType source
> bundle. After installation, all FreeType header files (including
> ft2build.h) are in the `<prefix>/include/freetype2' directory, and
> this is what you want, right?
Yes. Basically what I want is that the output of the following command:
$ PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --cflags freetype2
should NOT have "/usr/include" in it. Currently I get:
-I/usr/include/freetype2 -I/usr/include
Any way you can fix that while client source code not needing any change is
fine.
Thanks!
--
behdad
http://behdad.org/