From: "Denys Dmytriyenko" <denis@denix.org>
To: Joris Offouga <offougajoris@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-oe][PATCH] c-periphery: add recipe
Date: Sun, 7 Jun 2020 15:28:48 -0400 [thread overview]
Message-ID: <20200607192848.GS17660@denix.org> (raw)
In-Reply-To: <20200607160532.415655-1-offougajoris@gmail.com>
On Sun, Jun 07, 2020 at 06:05:32PM +0200, Joris Offouga wrote:
> Signed-off-by: Joris Offouga <offougajoris@gmail.com>
> ---
> .../c-periphery/c-periphery_2.2.1.bb | 21 +++++++++++++++++++
> 1 file changed, 21 insertions(+)
> create mode 100644 meta-oe/recipes-devtools/c-periphery/c-periphery_2.2.1.bb
>
> diff --git a/meta-oe/recipes-devtools/c-periphery/c-periphery_2.2.1.bb b/meta-oe/recipes-devtools/c-periphery/c-periphery_2.2.1.bb
> new file mode 100644
> index 000000000..b53cd6b19
> --- /dev/null
> +++ b/meta-oe/recipes-devtools/c-periphery/c-periphery_2.2.1.bb
> @@ -0,0 +1,21 @@
> +SUMMURY = "C-Periphery lib used to access GPIO, LED, PWM, SPI, I2C, MMIO, Serial"
> +DESCRIPTION = "A C library for peripheral I/O (GPIO, LED, PWM, SPI, I2C, MMIO, Serial) in Linux"
libsoc?
If this one gets in, should probably go to recipes-support where libsoc
lives...
> +HOMEPAGE = "https://github.com/vsergeev/c-periphery"
> +
> +SECTION = "libs"
> +
> +LICENSE = "MIT"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=4097ec544cf01e9c7cfc4bdf8e4ed887"
> +
> +SRC_URI = "git://github.com/vsergeev/c-periphery;protocol=https"
> +SRCREV = "c2aa7d164f87b807077daeeb3443a56b89e1d1c9"
> +
> +S = "${WORKDIR}/git"
> +
> +inherit cmake
> +
> +EXTRA_OECMAKE = "-DBUILD_SHARED_LIBS=ON"
> +
> +BBCLASSEXTEND = "native nativesdk"
> +
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2020-06-07 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 16:05 [meta-oe][PATCH] c-periphery: add recipe Joris Offouga
2020-06-07 19:28 ` Denys Dmytriyenko [this message]
2020-06-10 19:09 ` [oe] " Khem Raj
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=20200607192848.GS17660@denix.org \
--to=denis@denix.org \
--cc=offougajoris@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.