[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ft-devel] [freetype2] master 3ec6465: Explain how to build a PIC-en

From: Dmitry Timoshkov
Subject: Re: [ft-devel] [freetype2] master 3ec6465: Explain how to build a PIC-enabled version of FreeType.
Date: Sun, 28 Aug 2016 18:54:46 +0800

Werner LEMBERG <address@hidden> wrote:

> > What does mean?  Shared libraries are definitely PIC code.  Me not
> > understand.
> As written:
>   Setting this macro is needed for systems that prohibit address
>   fixups, such as BREW.
> gcc or clang is capable of automatically doing address fixups, BREW is
> not.
> I've just add this piece of information.

This is confusing. PIC support is a toolchain feature and has nothing to do
with support from the source code. In fact, marking the source directory or
module as not PIC capable is confusing even more.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]