[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:15:41 -0500 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 |
I have wanted to reply to this, but proper reply is very lengthy so it has
been sitting in my inbox. And now I truly regret not having replied before
you made the release.
On 13-11-13 03:19 AM, Werner LEMBERG wrote:
>
>> I like to suggest that ft2build.h be moved inside
>> ${includedir}/freetype2 also and freetype2.pc / freetype-config be
>> updated accordingly.
>
> I've done this now – and even more. From the ChangeLog:
>
> Simplify header file hierarchy.
>
> 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?
behdad
> one level. Since the file `ft2build.h' is also located in
> `include' (and it stays there even after installation), all
> FreeType header files are now in a single directory.
>
> Applications that use (a) `freetype-config' or FreeType's
> `pkg-config' file to get the include directory for the
> compiler, and (b) the documented way for header inclusion like
>
> #include <ft2build.h>
> #include FT_FREETYPE_H
> ...
>
> don't need any change to the source code.
>
> Hopefully, I've correctly updated all project files (and even
> `CMakeLists.txt') correctly. Please test.
>
> One issue remains: During installation, shall I do
>
> ln -s . freetype
>
> within the `/usr/local/include/freetype2' directory so that the old
> include file hierarchy is still available to all the people who don't
> follow (a) and (b) from above, for whatever reason?
>
>
> Werner
>
--
behdad
http://behdad.org/