[MacPorts] #20245: freetype variant for GNUstep

[MacPorts]

#20245: freetype variant for GNUstep
--------------------------------------+-------------------------------------
 Reporter:  and.damore@…              |       Owner:  ryandesign@…           
     Type:  enhancement               |      Status:  new                    
 Priority:  Normal                    |   Milestone:                         
Component:  ports                     |     Version:  1.7.1                  
 Keywords:  freetype gnustep variant  |        Port:  freetype               
--------------------------------------+-------------------------------------

Comment(by and.damore@…):

 I'm pasting a message from Wolfgang:

 "According to the freetype configure help message and a quick glance at
 its sources, --with-old-mac-fonts enables some code that uses (in one or
 the other way) the Carbon frameworks to access Mac fonts that are saved in
 the resource fork of a font file. This was common on Mac OS 9 and before,
 but Apple changed to dfonts in OS X, which save font data in the data fork
 and thus can be accessed with the normal *nix file system operation.
 Anyway, linking with the Carbon framework is a no-go for GNUstep since
 Tiger, as the Carbon frameworks (like virtually any Apple framework) link
 against CoreFoundation and the latter uses Apple's libobjc since the
 introduction of Tiger. This leads to programs with two incompatible
 Objective-C runtimes (the GNU one required by GNUstep and the Apple one
 brought in via CoreFoundation) that crash when one of the runtimes
 attempts to initialize the data structures of the other.

 I think a better name for the variant configured with --without-old-mac-
 fonts is puredarwin. This seems to be consistent with other ports that
 provide (or have provided, its been a while that I've last upgraded my
 MacPorts tree :-) variants that omit features which are specific to OS X.
 A slightly better description for the variant would be {remove support for
 resource-based fonts from classic Mac OS 9}. You may also want to check
 that this particular variant is installed in the Portfile of gnustep-gui.
 I seem to recall that the gnustep Portfiles do the same with respect to
 the nonls variant of aspell, but I can't find at present where this was
 done exactly.

 Incidentally, I feel that support for old style Mac fonts is obsolete and
 the decision to configure freetype with --with-old-mac-fonts by default is
 wrong; after all OS X no longer supports Classic since Leopard, and
 Leopard's font manager does not recognize the old fonts even if they are
 installed on a machine, but that is probably another story "

 This seems to show several points.

 Actually I rebuilt the gnustep core using freetype --with-old-mac-fonts
 option but then I didn't try to build an actual GNUstep application, I
 just built wmaker that doesn't actually use GNUstep, iirc.

 Unless you have a specific reason to use it I suggest to remove the option
 from '''macosx''' variant.

-- 
Ticket URL: <http://trac.macports.org/ticket/20245#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS