From: Ulf Samuelsson <openembedded@emagii.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Finding out the IMAGE_BASENAME of the image beeing built
Date: Sat, 30 Mar 2013 15:36:18 +0100 [thread overview]
Message-ID: <5156F862.6080005@emagii.com> (raw)
In-Reply-To: <CAPESJy7cfZvAePoLrVnvqoxaYRRxz1=U5L5ROP5MHbiWZEEBCA@mail.gmail.com>
On 2013-03-30 14:04, Takeshi Hamasaki wrote:
> Hi Ulf,
>
> $ MACHINE=beagleboard bitbake -e some-image
>
> shows all variables including $IMAGE_BASENAME without actually
> building the image.
> Using grep you can take the value of IMAGE_BASENAME, like as:
Thanks,
bitbake is already running to build my recipe.
Not sure that running "bitbake -e" is OK while bitbake is already running.
IMAGE_BASENAME is set to my recipe, so I cannot use this directly.
> $ MACHINE=beagleboard bitbake -e some-image | grep ^IMAGE_BASENAME
>
> Does it help you?
>
> If possible, consider to use hooks, for example, IMAGE_POSTPROCESS_COMMAND .
> Refer image.bbclass for details. It might make things straiter.
>
> Regards,
I know I can do it inside the "some-image.bb" recipe, but I would like
to do it inside my recipe. Otherwise all images must be customized
for my recipe, which is not a good idea.
If I could do an IMAGE_POSTPROCESS_COMMAND in my recipe, then
that would be OK, but I then still need to find out what the image name is.
BR
Ulf Samuelsson
next prev parent reply other threads:[~2013-03-30 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-30 12:32 Finding out the IMAGE_BASENAME of the image beeing built Ulf Samuelsson
2013-03-30 13:04 ` Takeshi Hamasaki
2013-03-30 14:36 ` Ulf Samuelsson [this message]
2013-03-30 14:13 ` Paul Eggleton
2013-03-30 21:01 ` Ulf Samuelsson
2013-04-01 13:09 ` Takeshi Hamasaki
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=5156F862.6080005@emagii.com \
--to=openembedded@emagii.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.