From: Bernhard Walle <bernhard@bwalle.de>
To: ptxdist@pengutronix.de
Cc: Bernhard Walle <walle@corscience.de>
Subject: [ptxdist] [PATCH] rules: Add fbterm
Date: Mon, 26 Mar 2012 22:07:21 +0200 [thread overview]
Message-ID: <1332792441-18367-1-git-send-email-bernhard@bwalle.de> (raw)
From: Bernhard Walle <walle@corscience.de>
This is a nice framebuffer terminal with support for Unicode and nice
font rendering.
Signed-off-by: Bernhard Walle <walle@corscience.de>
---
rules/fbterm.in | 12 +++++++++++
rules/fbterm.make | 57 +++++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 69 insertions(+)
create mode 100644 rules/fbterm.in
create mode 100644 rules/fbterm.make
diff --git a/rules/fbterm.in b/rules/fbterm.in
new file mode 100644
index 0000000..68013c0
--- /dev/null
+++ b/rules/fbterm.in
@@ -0,0 +1,12 @@
+## SECTION=multimedia_framebuffer
+
+config FBTERM
+ tristate
+ prompt "fbterm"
+ select FREETYPE
+ select FONTCONFIG
+ help
+ Framebuffer terminal. Supports unicode and uses fontconfig and Freetype
+ for font rendering. Thus is has support for anti-aliased fonts.
+
+# vim: set ts=8 sw=8 noet ft=kconfig:
diff --git a/rules/fbterm.make b/rules/fbterm.make
new file mode 100644
index 0000000..2737c41
--- /dev/null
+++ b/rules/fbterm.make
@@ -0,0 +1,57 @@
+# -*-makefile-*-
+#
+# Copyright (C) 2012 by Bernhard Walle <walle@corscience.de>
+#
+# See CREDITS for details about who has contributed to this project.
+#
+# For further information about the PTXdist project and license conditions
+# see the README file.
+#
+
+#
+# We provide this package
+#
+PACKAGES-$(PTXCONF_FBTERM) += fbterm
+
+#
+# Paths and names
+#
+FBTERM_VERSION := 1.7.0
+FBTERM_MD5 := c36bae75a450df0519b4527cccaf7572
+FBTERM := fbterm-$(FBTERM_VERSION)
+FBTERM_SUFFIX := tar.gz
+FBTERM_URL := http://fbterm.googlecode.com/files/$(FBTERM).$(FBTERM_SUFFIX)
+FBTERM_SOURCE := $(SRCDIR)/$(FBTERM).$(FBTERM_SUFFIX)
+FBTERM_DIR := $(BUILDDIR)/$(FBTERM)
+FBTERM_LICENSE := GPL v2
+
+# ----------------------------------------------------------------------------
+# Prepare
+# ----------------------------------------------------------------------------
+
+#
+# autoconf
+#
+FBTERM_CONF_TOOL := autoconf
+
+# ----------------------------------------------------------------------------
+# Target-Install
+# ----------------------------------------------------------------------------
+
+$(STATEDIR)/fbterm.targetinstall:
+ @$(call targetinfo)
+
+ @$(call install_init, fbterm)
+ @$(call install_fixup, fbterm,PRIORITY,optional)
+ @$(call install_fixup, fbterm,SECTION,base)
+ @$(call install_fixup, fbterm,AUTHOR,"Bernhard Walle <walle@corscience.de>")
+ @$(call install_fixup, fbterm,DESCRIPTION,missing)
+
+ @$(call install_copy, fbterm, 0, 0, 0755, \
+ -, /usr/bin/fbterm)
+
+ @$(call install_finish, fbterm)
+
+ @$(call touch)
+
+# vim: syntax=make
--
1.7.9.4
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2012-03-26 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 20:07 Bernhard Walle [this message]
2012-03-28 9:14 ` Michael Olbrich
2012-03-29 7:36 ` [ptxdist] [PATCH v2] " Bernhard Walle
2012-04-02 20:30 ` Michael Olbrich
2012-04-04 8:42 ` [ptxdist] [PATCH v3] " Bernhard Walle
2012-04-08 8:15 ` Michael Olbrich
2012-04-08 15:28 ` Bernhard Walle
2012-04-17 9:18 ` Michael Olbrich
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=1332792441-18367-1-git-send-email-bernhard@bwalle.de \
--to=bernhard@bwalle.de \
--cc=ptxdist@pengutronix.de \
--cc=walle@corscience.de \
/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