All of lore.kernel.org
 help / color / mirror / Atom feed
* Where do image names come from?
@ 2013-06-13 23:04 Paul D. DeRocco
  2013-06-14  1:26 ` Khem Raj
  0 siblings, 1 reply; 3+ messages in thread
From: Paul D. DeRocco @ 2013-06-13 23:04 UTC (permalink / raw)
  To: yocto

Where does the base name of the image files in build/tmp/deploy/images come
from? More to the point, if I create my own image recipe in my own layer,
what control do I have over the name of the resulting image files? I'd like
to be able to create more than one variant, and not have to remember which
is which based on the build times appended to the file names.

A related question: section 5.2.1 of the dev-manual says I can create a
custom image based on an existing image by copying that image recipe and
then modifying it. Is there some reason I can't use a .bbappend for this,
e.g., core-image-base.bbappend?

-- 

Ciao,               Paul D. DeRocco
Paul                mailto:pderocco@ix.netcom.com 
 



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Where do image names come from?
  2013-06-13 23:04 Where do image names come from? Paul D. DeRocco
@ 2013-06-14  1:26 ` Khem Raj
  2013-06-14  8:01   ` Paul Eggleton
  0 siblings, 1 reply; 3+ messages in thread
From: Khem Raj @ 2013-06-14  1:26 UTC (permalink / raw)
  To: Paul D. DeRocco; +Cc: yocto@yoctoproject.org

On Thu, Jun 13, 2013 at 4:04 PM, Paul D. DeRocco <pderocco@ix.netcom.com> wrote:
> Where does the base name of the image files in build/tmp/deploy/images come
> from? More to the point, if I create my own image recipe in my own layer,
> what control do I have over the name of the resulting image files? I'd like
> to be able to create more than one variant, and not have to remember which
> is which based on the build times appended to the file names.

IMAGE_BASENAME variable is used to define name. by default its same as
PN of image recipe.

>
> A related question: section 5.2.1 of the dev-manual says I can create a
> custom image based on an existing image by copying that image recipe and
> then modifying it. Is there some reason I can't use a .bbappend for this,
> e.g., core-image-base.bbappend?

you can but then its a different image. You dont have to copy you can
also include the existing image recipe
in your recipe and add customizations.

>
> --
>
> Ciao,               Paul D. DeRocco
> Paul                mailto:pderocco@ix.netcom.com
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Where do image names come from?
  2013-06-14  1:26 ` Khem Raj
@ 2013-06-14  8:01   ` Paul Eggleton
  0 siblings, 0 replies; 3+ messages in thread
From: Paul Eggleton @ 2013-06-14  8:01 UTC (permalink / raw)
  To: Paul D. DeRocco; +Cc: yocto

On Thursday 13 June 2013 18:26:10 Khem Raj wrote:
> On Thu, Jun 13, 2013 at 4:04 PM, Paul D. DeRocco <pderocco@ix.netcom.com>
> wrote:
> > Where does the base name of the image files in build/tmp/deploy/images
> > come from? More to the point, if I create my own image recipe in my own
> > layer, what control do I have over the name of the resulting image files?
> > I'd like to be able to create more than one variant, and not have to
> > remember which is which based on the build times appended to the file
> > names.
>
> IMAGE_BASENAME variable is used to define name. by default its same as
> PN of image recipe.

You should probably just have different image recipes for this - problem 
solved.
 
> > A related question: section 5.2.1 of the dev-manual says I can create a
> > custom image based on an existing image by copying that image recipe and
> > then modifying it. Is there some reason I can't use a .bbappend for this,
> > e.g., core-image-base.bbappend?
> 
> you can but then its a different image. You dont have to copy you can
> also include the existing image recipe in your recipe and add
> customizations.

The reasoning for documenting it that way is that usually image recipes are so 
trivial there's not much point in extending an existing recipe, plus you 
usually want to give it your own name; and if you did extend an existing 
recipe you would potentially pick up any changes to the original recipe which 
may not be desirable if you've already examined and approved the content of 
the image. Unlike other recipes most of the time it's just simpler and less 
maintenance to just copy and edit the image recipe as desired.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-06-14  8:01 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-06-13 23:04 Where do image names come from? Paul D. DeRocco
2013-06-14  1:26 ` Khem Raj
2013-06-14  8:01   ` Paul Eggleton

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.