Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] pkcs11-helper : add new recipe
Date: Tue, 9 Dec 2014 11:24:34 +0100	[thread overview]
Message-ID: <20141209102434.GE2470@jama> (raw)
In-Reply-To: <1417486264-1878-1-git-send-email-lixin.fnst@cn.fujitsu.com>

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

On Tue, Dec 02, 2014 at 10:11:04AM +0800, Li xin wrote:
> PKCS#11 is a published standard. PKCS#11 is the de-facto standard
> to access cryptographic devices.
> pkcs11-helper is a library that simplifies the interaction with
> PKCS#11 providers for end-user applications using a simple API
> and optional OpenSSL engine.

Fails to configure, check the logs from last world build.

> Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com>
> ---
>  .../pkcs11-helper/pkcs11-helper_1.11.bb            | 28 ++++++++++++++++++++++
>  1 file changed, 28 insertions(+)
>  create mode 100644 meta-oe/recipes-support/pkcs11-helper/pkcs11-helper_1.11.bb
> 
> diff --git a/meta-oe/recipes-support/pkcs11-helper/pkcs11-helper_1.11.bb b/meta-oe/recipes-support/pkcs11-helper/pkcs11-helper_1.11.bb
> new file mode 100644
> index 0000000..9d08d25
> --- /dev/null
> +++ b/meta-oe/recipes-support/pkcs11-helper/pkcs11-helper_1.11.bb
> @@ -0,0 +1,28 @@
> +SUMMARY = "A library for using PKCS"
> +DESCRIPTION = "pkcs11-helper is a library that simplifies the interaction with PKCS \
> +providers for end-user applications using a simple API and optional OpenSSL \
> +engine. The library allows using multiple PKCS enumerating available token \
> +certificates, or selecting a certificate directly by serialized id, handling \
> +card removal and card insert events, handling card ie-insert to a different \
> +slot, supporting session expiration and much more all using a simple API."
> +
> +HOMEPAGE = "git://github.com/OpenSC/pkcs11-helper.git"
> +SECTION = "Development/Libraries"
> +
> +LICENSE = "GPLv2 BSD"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=4948810631bcac142af53d32df5b6ee1 \
> +    file://COPYING.GPL;md5=8a71d0475d08eee76d8b6d0c6dbec543 \
> +    file://COPYING.BSD;md5=f79f90ea7a106796af80b5d05f1f8da1"
> +
> +SRC_URI = "git://github.com/OpenSC/pkcs11-helper.git"
> +SRC_URI[md5sum] = "9f62af9f475901b89355266141306673"
> +SRC_URI[sha256sum] = "494ec59c93e7c56c528f335d9353849e2e7c94a6b1b41c89604694e738113386"
> +
> +S = "${WORKDIR}/git"
> +SRCREV = "e7adf8f35be232a4f04c53b4ac409be52792093e"
> +
> +DEPENDS = "zlib nettle gnutls gmp openssl"
> +
> +inherit autotools pkgconfig
> +
> +EXTRA_OECONF = " --disable-static --enable-doc "
> -- 
> 1.8.4.2
> 
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2014-12-09 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02  2:11 [meta-oe][PATCH] pkcs11-helper : add new recipe Li xin
2014-12-09 10:24 ` Martin Jansa [this message]
2015-01-15  1:17   ` [meta-oe][PATCH v2] pkcs11-helper: " Li xin

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=20141209102434.GE2470@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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