public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps <cygwin-apps@cygwin.com>
Subject: [ITA from Yaakov] graphite2
Date: Mon, 11 May 2020 15:03:56 -0400	[thread overview]
Message-ID: <01c84072-5540-62ba-fc67-db6c99539db8@cornell.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 158 bytes --]

My cygport file is attached.  It is the same as Yaakov's, except for a version 
bump to the latest upstream release and an update of two of the patches.

Ken

[-- Attachment #2: graphite2.cygport --]
[-- Type: text/plain, Size: 989 bytes --]

inherit cmake

NAME="graphite2"
VERSION=1.3.14
RELEASE=1
CATEGORY="Libs"
SUMMARY="Graphite smart font parser"
DESCRIPTION="Graphite is a package that can be used to create smart fonts
capable of displaying writing systems with various complex behaviors.
A smart font contains not only letter shapes but also additional instructions
indicating how to combine and position the letters in complex ways."
HOMEPAGE="http://graphite.sil.org/"
SRC_URI="mirror://sourceforge/silgraphite/graphite2-${VERSION}.tgz"
PATCH_URI="
	1.3.14-1-cygwin.patch
	1.3.14-1-as-needed.patch
	03-cmakepath.patch
"

BUILD_REQUIRES="asciidoc cmake doxygen libfreetype-devel"

PKG_NAMES="graphite2 libgraphite2_3 libgraphite2-devel"
graphite2_CATEGORY="Graphics"
graphite2_CONTENTS="usr/bin/gr2fonttest.exe usr/share/doc/"
libgraphite2_3_CONTENTS="usr/bin/cyggraphite2-3.dll"
libgraphite2_devel_CONTENTS="
	usr/include/graphite2/
	usr/lib/cmake/graphite2/
	usr/lib/libgraphite2.dll.a
	usr/lib/pkgconfig/graphite2.pc
"

             reply	other threads:[~2020-05-11 19:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 19:03 Ken Brown [this message]
2020-05-11 19:46 ` Marco Atzeri

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=01c84072-5540-62ba-fc67-db6c99539db8@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).