On 2008-07-07 , at 11:53 , Ryan Schmidt wrote:
>> The way I read things is that if one turns off quickdraw in freetype
>> then the "problem" will not occur.
>
> What are the implications of turning off QuickDraw in FreeType? What
> features will then not work?
From what I can see? No more deprecated QuickDraw functions. The
following configuration settings seem relevant...
--with-old-mac-fonts allow Mac resource-based fonts to be used
--with-fsspec use obsolete FSSpec API of MacOS, if
available
(default=yes)
--with-fsref use Carbon FSRef API of MacOS, if available
(default=yes)
--with-quickdraw-toolbox
use MacOS QuickDraw in ToolBox, if available
(default=yes)
--with-quickdraw-carbon use MacOS QuickDraw in Carbon, if available
(default=yes)
--with-ats use AppleTypeService, if available
(default=yes)
I modified my version of the Portfile (running from trunk)
--with-fsspec=no
--with-fsref=no
--with-quickdraw-toolbox=no
--with-quickdraw-carbon=no
--with-old-mac-fonts=no //this one is for me, since I don't use old
mac fonts ;-)
and left --with-ats alone.
Followed with
sudo port configure freetype
sudo port build freetype
sudo port install -f freetype
hand tested PHP, works as advertised.
sudo /opt/local/apache2/bin/apachectl graceful
tested the same PHP code with web browser. I got an image with text on
it as expected (the same image that gets produced by a running the PHP
straight-up).
From what I read the only "feature" that doesn't work anymore is the
ability to use freetype with old-style Mac file specs and references.
Anyway - I was just taking the opportunity to look into MacPorts in
more depth. I don't have any attachment to a change or not change in
the freetype port.
8)
----------------------------------
Chris Janton - face at CentosPrime dot COM
Netminder for Opus1.COM
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
