Re: [Devel] MacOS X and FT_New_Face

[Dan Williams]

Hi,

However, people must realize that on OS X you still need access to 
resource-based OS 9 fonts.  Not everything is a .dfont and OS X will 
still recognize all your resource-based fonts from your OS 9 fonts 
folder, along with resource-based fonts in your OS X font folders.  
Therefore, this #define is still needed on OS X.

Dan

On Tuesday, May 6, 2003, at 03:22  PM, Derk-Jan Hartman wrote:

> I ran into this problem.
> > Riccardo Cohen wrote:
> > > with my version (2.1.2) I had to comment the line 112 #define 
> > > FT_MACINTOSH 1 in file include/freetype/config/ftconfig.h because 
> > > this line make it consider macosx like macos9 from the ft_new_face 
> > > point of view, which is wrong.
> > It seems this definition is encapsulated in a test. The code is:
> >    #if defined( __APPLE__ ) || ( defined( __MWERKS__ ) && defined( 
> > macintosh ) )
> >    #define FT_MACINTOSH 1
> >    #endif
> >
> > We probably need a better test to disable this on MacOS-X.
> > Or should we compiled *both* FT_New_Face and the MacOS specific APIs
> > on MacOS-X ? (A small new configuration macro would be required then,
> > but that's nothing really difficult).
> >
> > Any ideas ?
>
> May i suggest the following construction ???
> __APPLE__ && !(__mach__ )
> That would keep it undefined on the OSX platform when you compile it 
> as unix code.
> which is at least better then the current situation.
>
> DJ
>
> ---
> Videolan - VLC media player
> Derk-Jan Hartman (address@hidden)
> Co-Developer of the MacOS X port of vlc
> http://www.videolan.org/vlc
>
>
> _______________________________________________
> Devel mailing list
> address@hidden
> http://www.freetype.org/mailman/listinfo/devel