but there were still some bitmap fonts that failed to load correctly.
Instead, I will revert the portion of libXft that enforces strict bitmap
font sizes.
problems people were seeing with bitmap fonts after the big font upgrade
a few days ago.
Note: If you applied my libXft patch, you need to back that out once you
upgrade freetype2.
Obtained from: FreeType CVS
Begin autotools sanitization sequence by requiring ports to explicitly
specify which version of {libtool,autoconf,automake} they need, erasing
the concept of a "system default".
For ports-in-waiting:
USE_LIBTOOL=YES -> USE_LIBTOOL_VER=13
USE_AUTOCONF=YES -> USE_AUTOCONF_VER=213
USE_AUTOMAKE=YES -> USE_AUTOMAKE_VER=14
Ports attempting to use the old style system after June 1st 2004 will be
sorely disappointed.
and fontconfig. With this update, fc-cache takes no more that 2.1 MB
when running against full XFree fonts as well as webfonts, URW fonts,
and a collection of Internet-downloaded TrueType fonts.
PR: 50791
Submitted by: anholt and myself
Approved by: sobomax (maintainer)
gzip'd fonts. The next release of freetype2 will allow building with
the system version of zlib, so this won't be an issue.
Reported by: alane
Obtained from: FreeType CVS and /usr/src/lib/libz/infcodes.c
Approved by: maintainer
freetype library, and it helps the antialiased font stuff. There are no
drawbacks, other than unclear legal status (Apple holds some patents in
this area), but as long as it is OK for XFree, it should be OK for us too.
Submitted by: Jeremy Norris <ishmael27@home.com>
Makefiles abuse this variable commonly used to specify default
options for the top(1) monitor, which breaks the build.
PR: 25192
Submitted by: Stefan `Sec` Zehl <sec@42.org> (among several other, whose
names were lost in entropy
of Universe)
Several notes:
o Freetype2 is incompatible at API level with older freetype, therefore
portname will be freetype2-x.x to allow pkg_* tools correctly handle
dependencies (I do not use NO_LATEST_LINK, because it is a production-quality
software, not a beta or such).
o There are no fs namespace conflicts between freetype and freetype2, so they
both could be installed on the same machine w/o any problems.
previous commit message to bsd.port.mk, which said INSTALL_SHLIBS. Boo.)
Line up the rhs of variable assignments nicely. Remove a couple of extra
whitespaces while I'm here.
Suggested by: sobomax
For now, include files are installed in ${PREFIX}/include/freetype
(that's the default with version 1.3) and symlinks are created in
${PREFIX}/include for compatibility
