From: Wolfram Sang <w.sang@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Kjell Ove Røte" <Kjell.Ove.Rote@zenitel.com>,
"Eivind Versvik" <eivind.versvik@zenitel.com>
Subject: [ptxdist] [PATCH] rules: add libosip2
Date: Wed, 21 Mar 2012 09:33:42 +0100 [thread overview]
Message-ID: <1332318822-22111-1-git-send-email-w.sang@pengutronix.de> (raw)
Signed-off-by: Eivind Versvik <eivind.versvik@zenitel.com>
Signed-off-by: Kjell Ove Røte <Kjell.Ove.Rote@zenitel.com>
Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
---
rules/libosip2.in | 7 ++++++
rules/libosip2.make | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 62 insertions(+), 0 deletions(-)
create mode 100644 rules/libosip2.in
create mode 100644 rules/libosip2.make
diff --git a/rules/libosip2.in b/rules/libosip2.in
new file mode 100644
index 0000000..4483bbc
--- /dev/null
+++ b/rules/libosip2.in
@@ -0,0 +1,7 @@
+## SECTION=system_libraries
+
+config LIBOSIP2
+ tristate
+ prompt "libosip2"
+ help
+ The GNU oSIP library is an implementation of SIP - rfc3261
diff --git a/rules/libosip2.make b/rules/libosip2.make
new file mode 100644
index 0000000..3d2a372
--- /dev/null
+++ b/rules/libosip2.make
@@ -0,0 +1,55 @@
+# -*-makefile-*-
+#
+# Copyright (C) 2012 by Eivind Versvik <eivind.versvik@zenitel.com>
+# Copyright (C) 2012 by Wolfram Sang <w.sang@pengutronix.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_LIBOSIP2) += libosip2
+
+#
+# Paths and names
+#
+LIBOSIP2_VERSION := 3.3.0
+LIBOSIP2_MD5 := 81493bb4d4ae6d55b71a0d4369339125
+LIBOSIP2 := libosip2-$(LIBOSIP2_VERSION)
+LIBOSIP2_SUFFIX := tar.gz
+LIBOSIP2_URL := $(call ptx/mirror, GNU, osip/$(LIBOSIP2).$(LIBOSIP2_SUFFIX))
+LIBOSIP2_SOURCE := $(SRCDIR)/$(LIBOSIP2).$(LIBOSIP2_SUFFIX)
+LIBOSIP2_DIR := $(BUILDDIR)/$(LIBOSIP2)
+LIBOSIP2_LICENSE := LGPLv2.1+
+
+# ----------------------------------------------------------------------------
+# Prepare
+# ----------------------------------------------------------------------------
+
+LIBOSIP2_CONF_TOOL := autoconf
+
+# ----------------------------------------------------------------------------
+# Target-Install
+# ----------------------------------------------------------------------------
+
+$(STATEDIR)/libosip2.targetinstall:
+ @$(call targetinfo)
+
+ @$(call install_init, libosip2)
+ @$(call install_fixup, libosip2, PRIORITY, optional)
+ @$(call install_fixup, libosip2, SECTION, base)
+ @$(call install_fixup, libosip2, AUTHOR, "Eivind Versvik <eivind.versvik@zenitel.com>")
+ @$(call install_fixup, libosip2, DESCRIPTION, missing)
+
+ @$(call install_lib, libosip2, 0, 0, 0644, libosip2)
+ @$(call install_lib, libosip2, 0, 0, 0644, libosipparser2)
+
+ @$(call install_finish, libosip2)
+
+ @$(call touch)
+
+# vim: syntax=make
--
1.7.9.1
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2012-03-21 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 8:33 Wolfram Sang [this message]
2012-03-21 9:08 ` Juergen Beisert
2012-03-21 9:15 ` Wolfram Sang
2012-03-21 9:23 ` Juergen Beisert
2012-03-21 10:37 ` Wolfram Sang
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=1332318822-22111-1-git-send-email-w.sang@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=Kjell.Ove.Rote@zenitel.com \
--cc=eivind.versvik@zenitel.com \
--cc=ptxdist@pengutronix.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