Hi, Thanks for the info. I'm planning to use Freetype with a smaller 64 bit os that follows the LP64 model.
I'm sure you already know this, but just for the sake of completeness, LP64 means it will use 32 bit ints, 64 bit longs, 64 bit long longs, 64 bit pointers, size_t=64, etc. So, if I understand you correctly, it appears I can make all necessary adjustments in the ftconfig.h header file. Is this correct? Thanks, Richard -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, June 27, 2008 3:44 PM To: Memory, Richard Cc: [email protected] Subject: Re: [ft] Freetype and 64bit Hi, On Fri, 27 Jun 2008 13:37:23 -0700 "Memory, Richard" <[EMAIL PROTECTED]> wrote: >What is Freetype's situation with respect to 64 bit operating systems? >Has it been tested/used on a 64 bit system? Yet I'm not sure what kind of systems you're thinking of, FreeType2 is already known to run on several amd64 systems: GNU/Linux on amd64, FreeBSD on amd64, Mac OS X on amd64, etc. Also I'm sure that FreeType2 was running on Unix-like systems and OpenVMS on legacy Alpha CPU. One of the problem is that bit length of char, int, long (FT_SIZEOF_INT, FT_SIZEOF_LONG, FT_SIZEOF_CHAR) are statically defined by ftconfig.h. The file is written for each platforms (Win32, Amiga, VMS, ...), or statically configured by running configure script when the library is built. Some people wants single ftconfig.h to switch these values dynamically (in the other words, they are expected to be defined by the compilers internal macros like __LP64__ etc). It's my task but not solved yet, I'm looking for reliable standard... Regards, mpsuzuki _______________________________________________ Freetype mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/freetype
