All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: Matteo Facchinetti <matteo.facchinetti@sirius-es.it>,
	yocto@yoctoproject.org
Subject: Re: require and image.bbappend
Date: Thu, 4 Apr 2019 17:31:58 +0200	[thread overview]
Message-ID: <036ebe30-ce24-9e66-9e00-b6431023946c@denx.de> (raw)
In-Reply-To: <CAAjAsixRKTj9pt1gSC5cT149Y4Kgy5WYxjLmWRU9z9LhY-2-ww@mail.gmail.com>

Hi Matteo,

On 04/04/19 15:35, Matteo Facchinetti wrote:
> Hi,
> 
> I encountered a problem when try to add packages in my image recipe, but
> I don't understernd if I wrong something or I have to do it in another way.
> 
> In detail, in my common_layer there are:
>    - image_base.bb <http://image_base.bb> : yocto base image 
>    - image_with_graphicsupport.bb <http://image_with_graphicsupport.bb>
> : where include image_base.bb <http://image_base.bb> (require
> image_base.bb <http://image_base.bb>)
> 
> Now, in my BSP layer, I want to add some packages to the image_base.bb
> <http://image_base.bb>, so I create here the image_base.bbappend file.
> But when I try to compile image_with_graphicsupport.bb
> <http://image_with_graphicsupport.bb> the result is not how expected.
> Image_with_graphicsupport.bb doesn't add packages contained in
> image_base.bbappend but only the packages contained in image_base.bb
> <http://image_base.bb>.
> 
> Is true that when include an image to another with require statement,
> you can't extend the base image with a bbappend?

Yes, it is true, because the file is included and it is not anymore like
a recipe that can be extend. It will be searched for a
image_with_graphicsupport.bb append, not image_base.bbappend.

IMHO you can easy reach your goal if you write a packagegroup recipe
where you put all packages you have in the IMAGE_INSTALL of your
image_base.bb. You can then have a .bbappend for the packagegroup in
your BSP layer (and this then works) and you put the packagegroup in the
IMAGE_INSTALL directive of both image_base.bb and
Image_with_graphicsupport.bb.

> or I wrong something else?
> 

Best regards,
Stefano Babic


-- 
=====================================================================
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================


  reply	other threads:[~2019-04-04 15:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 13:35 require and image.bbappend Matteo Facchinetti
2019-04-04 15:31 ` Stefano Babic [this message]
2019-04-05 15:54   ` Matteo Facchinetti
2019-04-05 16:33     ` Stefano Babic
2019-04-05 21:44       ` Matteo Facchinetti

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=036ebe30-ce24-9e66-9e00-b6431023946c@denx.de \
    --to=sbabic@denx.de \
    --cc=matteo.facchinetti@sirius-es.it \
    --cc=yocto@yoctoproject.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.