Re: [ft-devel] Minor misc patches to freetype cvs, from custom changes in vtk

2007-03-21 Thread Werner LEMBERG

 I have been working on updating VTK (www.vtk.org) from freetype
 2.1.9 to the 2.3.2.  It has gone pretty smoothly, thanks in part to
 the detailed changelogs you guys keep, thank you!

I invest a considerable amount of time to maintain them...


Werner


___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel


Re: [ft-devel] Minor misc patches to freetype cvs, from custom changes in vtk

2007-03-21 Thread mpsuzuki
Dear Sir,

Now I'm going to commit your patch to CVS head,
but I have small question.

Your patch to builds/unix/ftconfig.in will disable
Carbon support on 64bit ABI in Intel Mac.
It means that the resource-fork based font support
(ftmac.c) are unavailable completely. Not only
deprecated QuickDraw and FileManager (FSSpec etc)
functions, but also ATS and FSRef functions.
It is intended design?

Regards,
mpsuzuki

On Tue, 20 Mar 2007 11:24:49 -0400
Sean McBride [EMAIL PROTECTED] wrote:
 On 3/20/07 9:56 AM, [EMAIL PROTECTED] said:
 
  1) builds/unix/ftconfig.in
   - minor Mac fix, test against __LP64__ not __ppc64__.  There are also
  64 bit Intel CPUs.
 
 Thank you for notice 64bit API in Intel Mac,
 yet I don't have that.
 
 #if __LP64__
 ...
 #endif
 
 might be simpler, how do you think?
 
 As David said, I do this to prevent a warning from gcc's -wundef.  Apple
 is inconsistent in their own headers.  Sometimes they do #if __LP64__
 sometimes they do #ifdef __LP64__.  I suspect __LP64__ is either not
 defined at all, or defined to 1.


___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel


Re: [ft-devel] Minor misc patches to freetype cvs, from custom changes in vtk

2007-03-21 Thread Miles Bader
David Turner [EMAIL PROTECTED] writes:
 this will generate an error with certain compilers/pre-processors if
 __LP64__ is not defined.  generally speaking #if X is not a
 portable statement, except if you ensure that the macro is always
 defined beforehand.

Is this true according to the C standard, or a problem with any
non-obsolete compilers?

[I ask because such usage is widespread, and although gcc has a warning for
it, it doesn't get turned on even with -ansi -pedantic -Wall -Wextra,
you have to enable it explicitly.]

-Miles

-- 
Ich bin ein Virus. Mach' mit und kopiere mich in Deine .signature.



___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel