[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [ft-devel] ftconfig.h in LSB
From: |
Camp, TracyX E |
Subject: |
RE: [ft-devel] ftconfig.h in LSB |
Date: |
Wed, 13 Dec 2006 07:45:06 -0800 |
>-----Original Message-----
>From: address@hidden [mailto:address@hidden
>Sent: Tuesday, December 12, 2006 9:15 PM
>To: Camp, TracyX E
>Cc: address@hidden
>Subject: Re: [ft-devel] ftconfig.h in LSB
>
>Hi,
>
>On Tue, 12 Dec 2006 11:11:27 -0800
>"Camp, TracyX E" <address@hidden> wrote:
>>Are there any cases where (say macros), depend on the defines in
>>ftconfig.h?
>>
>>fttypes.h seems to nicely encapsulate the API/ABI types independantly
>>from ftconfig.h. Bad/Good assumption?
>
>32/64bit issues may arise. Check the discussion on 2005,
>
>http://lists.gnu.org/archive/html/freetype-devel/2005-12/msg00014.html
Thank you for the pointer. I'm not sure that entirely answers my
question. I'm more or less proposing to leave ftconfig.h entirely out
of the LSB specification. I'm trying to determine what impact
ftconfig.h has on the API/ABI since it appears that the types used in
the public API are defined in fttypes.h exclusively.
FYI, LSB handles multiple-arches by installing multiple LSB dev packages
at different file system locations. The lsb build tool 'lsbcc' then
sets up the build to use the LSB installed headers for whatever arch
over system installed headers.
Thanks,
Tracy Camp
>
>Regards,
>mpsuzuki
>