All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dvorkin Dmitry <dvorkin@tibbo.com>
To: openembedded-core@lists.openembedded.org
Subject: two recipes, one replaces files of another
Date: Tue, 15 Aug 2017 13:37:45 +0300	[thread overview]
Message-ID: <3ce69269-11b4-34b8-68fe-0ce8ac9bd103@tibbo.com> (raw)
In-Reply-To: <1503655141-1302-1-git-send-email-stefan@agner.ch>

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

Good time of day, people!

I have two recipes for two cases:
recipe-brdRevA.bb
recipe-brdRevB.bb

both of them has one file:
/etc/myprog/c.conf

and two image definition files:
imgA.bb
imgB.bb

, that requires recipe-brdRevA.bb or recipe-brdRevB.bb indirectly by 
IMAGE_INSTALL += "myprog"

myprog.bb requires files from recipe-brdRevA or recipe-brdRevB, 
depending on image.

It's not a correct idea to add IMAGE_INSTALL += "recipe-brdRev<N>" into 
img<N>.bb explicitely.

How to create dependencies correctly?
I try to add
RPROVIDES_${PN} += "recipe-brd" in both recipe-brdRevA/B  and use 
PREFERRED_PROVIDER_recipe-brd = "..."
into imgA/B.bb without success.

Please, advice me.



[-- Attachment #2: dvorkin.vcf --]
[-- Type: text/x-vcard, Size: 315 bytes --]

begin:vcard
fn:Dmitry Dvorkin
n:Dvorkin;Dmitry
org:Tibbo Technology Inc.;Tibbo Engeneering
adr:;;9F-3, No.31, Lane 169, Kang-Ning St., Hsi-Chih, New Taipei City;Taipei;Taipei;22180;Taiwan
email;internet:dvorkin@tibbo.com
title:Embedded Linux System Architect
url:http://tibbo.com/
version:2.1
end:vcard


  parent reply	other threads:[~2017-08-15 10:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25  9:59 [PATCH] image.bbclass: delete DATE variable too Stefan Agner
2017-08-11  3:31 ` ✗ patchtest: failure for " Patchwork
2017-08-15 10:37 ` Dvorkin Dmitry [this message]
2017-08-15 10:59   ` two recipes, one replaces files of another Alexander Kanavin
2017-08-15 14:21     ` Dvorkin Dmitry
2017-08-15 14:38       ` Alexander Kanavin
2017-08-18  6:16         ` Dvorkin Dmitry

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=3ce69269-11b4-34b8-68fe-0ce8ac9bd103@tibbo.com \
    --to=dvorkin@tibbo.com \
    --cc=openembedded-core@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.