From: "Belal, Awais" <Awais_Belal@mentor.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] grub_git: extend recipe for proper target deployment
Date: Wed, 14 Dec 2016 13:29:57 +0000 [thread overview]
Message-ID: <1481722196426.25330@mentor.com> (raw)
In-Reply-To: <CAJTo0LZOSS8nYB9ooPsSJGkuBU5=pvzCTUAKVXSEUR=f7kgjDg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
Hi Ross,
>> +RDEPENDS_${PN}_class-target = "diffutils freetype"
> Does this really need to be class-target-specific?
Without the class-target override I get
ERROR: Nothing RPROVIDES 'diffutils-native' (but virtual:native:/data/amd_yocto/poky/meta/recipes-bsp/grub/grub_git.bb RDEPENDS on or otherwise requires it)
so I believe this is necessary in this case. Are you through your review? If so, just let me know and I'll send a v2 fixing the other DEPENDS issue you pointed out.
BR,
Awais
________________________________
From: Burton, Ross <ross.burton@intel.com>
Sent: Tuesday, December 13, 2016 7:17 PM
To: Belal, Awais
Cc: OE-core
Subject: Re: [OE-core] [PATCH 1/2] grub_git: extend recipe for proper target deployment
On 13 December 2016 at 11:19, Awais Belal <awais_belal@mentor.com<mailto:awais_belal@mentor.com>> wrote:
+DEPENDS_class-target += "grub-native"
The native magic won't generate dependencies on itself, so this can just be DEPENDS.
+RDEPENDS_${PN}_class-target = "diffutils freetype"
Does this really need to be class-target-specific?
Ross
[-- Attachment #2: Type: text/html, Size: 3042 bytes --]
prev parent reply other threads:[~2016-12-14 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 11:19 [PATCH 1/2] grub_git: extend recipe for proper target deployment Awais Belal
2016-12-13 11:19 ` [PATCH 2/2] grub-efi/live-vm-common: allow grub as EFI_PROVIDER Awais Belal
2016-12-13 14:17 ` [PATCH 1/2] grub_git: extend recipe for proper target deployment Burton, Ross
2016-12-14 13:29 ` Belal, Awais [this message]
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=1481722196426.25330@mentor.com \
--to=awais_belal@mentor.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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