From: Khem Raj <raj.khem@gmail.com>
To: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] fftw: Allow an empty package for fftw.
Date: Fri, 21 Oct 2016 10:08:25 -0700 [thread overview]
Message-ID: <36CFFABF-F18A-405E-BA43-08713EC46478@gmail.com> (raw)
In-Reply-To: <1477052056-14472-1-git-send-email-philip@balister.org>
[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]
> On Oct 21, 2016, at 5:14 AM, Philip Balister <philip@balister.org> wrote:
>
> The fftw-dev package RDEPENDS on the fftw package. Let the recipe create an
> empty one to satisfy this requirement.
>
> Signed-off-by: Philip Balister <philip@balister.org>
> ---
> meta-oe/recipes-support/fftw/fftw_3.3.4.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta-oe/recipes-support/fftw/fftw_3.3.4.bb b/meta-oe/recipes-support/fftw/fftw_3.3.4.bb
> index 0faaea1..0bb6cc2 100644
> --- a/meta-oe/recipes-support/fftw/fftw_3.3.4.bb
> +++ b/meta-oe/recipes-support/fftw/fftw_3.3.4.bb
> @@ -69,4 +69,6 @@ FILES_fftwl-wisdom = "${bindir}/fftwl-wisdom"
> FILES_fftwf-wisdom = "${bindir}/fftwf-wisdom"
> FILES_fftw-wisdom-to-conf = "${bindir}/fftw-wisdom-to-conf"
>
> +ALLOW_EMPTY_${PN}= “1"
as Martin said
RDEPENDS_${PN}-dev = “”
should be done.
> +
> BBCLASSEXTEND = "native"
> --
> 2.5.5
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2016-10-21 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 12:14 [meta-oe][PATCH] fftw: Allow an empty package for fftw Philip Balister
2016-10-21 16:41 ` Martin Jansa
2016-10-21 17:08 ` Khem Raj [this message]
2016-10-21 23:05 ` Philip Balister
2016-10-21 23:29 ` Khem Raj
2016-10-24 15:43 ` Martin Jansa
2016-10-24 16:10 ` Philip Balister
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=36CFFABF-F18A-405E-BA43-08713EC46478@gmail.com \
--to=raj.khem@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.