From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps <cygwin-apps@cygwin.com>
Subject: [ITA from Yaakov] freeport2
Date: Tue, 12 May 2020 12:50:48 -0400 [thread overview]
Message-ID: <e7a97f77-a2b3-a65d-e27f-0afd92f11af2@cornell.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
My cygport file is attached. Aside from some trivial URL changes, it differs
from Yaakov's as follows:
1. I've bumped the version from 2.9.1 to 2.10.2, the latest upstream release.
2. I removed the Fedora patch freetype-2.9-ftsmooth.patch, which is no longer
used in the Fedora build.
3. I removed the line 'cygmake refdoc', which was previously used to build the
API reference manual. The html files are now included in the source tarball.
The refdoc target is apparently now only needed for a build from the upstream
git repo.
Ken
[-- Attachment #2: freetype2.cygport --]
[-- Type: text/plain, Size: 1961 bytes --]
NAME="freetype2"
VERSION=2.10.2
RELEASE=1
CATEGORY="Libs"
SUMMARY="FreeType font engine"
DESCRIPTION="FreeType 2 is a software font engine that is designed to be small,
efficient, and highly customizable while capable of producing
high-quality output (glyph images)."
HOMEPAGE="http://freetype.sourceforge.net/"
SRC_URI="mirror://sourceforge/freetype/freetype-${VERSION}.tar.xz
mirror://sourceforge/freetype/freetype-doc-${VERSION}.tar.xz
mirror://sourceforge/freetype/ft2demos-${VERSION}.tar.xz"
SRC_DIR="freetype-${VERSION}"
PATCH_URI="
https://src.fedoraproject.org/cgit/rpms/freetype.git/plain/freetype-2.3.0-enable-spr.patch
https://src.fedoraproject.org/cgit/rpms/freetype.git/plain/freetype-2.2.1-enable-valid.patch
https://src.fedoraproject.org/cgit/rpms/freetype.git/plain/freetype-2.6.5-libtool.patch
"
PKG_NAMES="${NAME}-demos libfreetype6 libfreetype-devel libfreetype-doc"
freetype2_demos_SUMMARY="${SUMMARY} (demo programs)"
freetype2_demos_CONTENTS="usr/bin/ft*.exe* usr/bin/tt*.exe"
libfreetype6_CONTENTS="--exclude=html usr/bin/*.dll usr/share/doc/"
libfreetype_devel_CONTENTS="usr/include/ usr/lib/ usr/share/aclocal/"
libfreetype_doc_CATEGORY="Doc"
libfreetype_doc_CONTENTS="usr/share/doc/${NAME}/html/"
DIFF_EXCLUDES='aclocal.m4 configure *.html'
src_compile() {
cd ${S}/builds/unix
NO_AUTOHEADER=1 \
ACLOCAL_FLAGS="-I ." \
cygautoreconf
mkdir -p ${B}/freetype2
lndir ${S} ${B}/freetype2
cd ${B}/freetype2
CYGCONF_SOURCE=${B}/freetype2
# harfbuzz: new in 2.5.3, circular dep
cygconf --with-zlib --with-bzip2 --with-png --without-harfbuzz
cygmake all
mkdir -p ${B}/ft2demos
lndir ${S}/../ft2demos-${PV} ${B}/ft2demos
cd ${B}/ft2demos
cygmake
}
src_install() {
local d
cd ${B}/freetype2
cyginstall
cd ${B}/ft2demos
dobin bin/*.exe
cd ${S}/docs
dodoc [A-HJ-Z]* *.txt
docinto html
dodoc ft2faq.html
for d in design glyphs reference tutorial
do
docinto html/${d}
dodoc ${d}/*
done
}
next reply other threads:[~2020-05-12 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 16:50 Ken Brown [this message]
2020-05-12 16:53 ` Ken Brown
2020-05-12 18:08 ` Marco Atzeri
2020-05-12 18:34 ` Ken Brown
2020-05-12 19:00 ` Marco Atzeri
2020-05-12 18:02 ` [ITA from Yaakov] freetype2 Yaakov Selkowitz
2020-05-12 18:46 ` Ken Brown
2020-10-20 14:46 ` libfreetype CVE FYI Brian Inglis
2020-10-20 18:00 ` Ken Brown
2020-10-21 17:03 ` Achim Gratz
2020-10-21 21:20 ` Ken Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e7a97f77-a2b3-a65d-e27f-0afd92f11af2@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).