This is the mail archive of the libffi-discuss@sourceware.org mailing list for the libffi project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Headers installation into libdir?


On Sat, Jul 3, 2010 at 1:50 PM, Samuli Suominen <ssuominen@gentoo.org> wrote:
> On 07/03/2010 07:26 PM, Luis Lavena wrote:
>> Hello,
>>
>> I was wondering why libffi 3.0.9 and current master (in GitHub) both
>> install ffi.h and ffitarget.h into libdir/libffi-X.Y.Z/include
>> directory?
>>
>> I believe that specific behavior is not good for packagers or users
>> trying to install libffi for normal usage.
>>
>> Please find attached a patch against master that corrects this behavior.
>>
>> Thank you.
>
> It's because the headers are archtype specific, libdir is the correct
> place for them, use pkg-config in your projects, like `pkg-config
> --cflags libffi` to get the include dir
>
> (btw, I also replied to you off-list before this reply by accident)
>

Thank you.

However, I see this as a problem. For example, when installing libffi
uisng macports, the include files are available directly without the
explicit need of pkg-config

Also, the lack of fully working/functional pkg-config will complicate
libffi usage on Windows platform using GCC for compilation.

How these package managers make the include file directly available?

Thank you.
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]