Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: special post build step for u-boot?
Date: Fri, 30 Apr 2010 15:35:27 +0200	[thread overview]
Message-ID: <4BDADC9F.9000406@dresearch.de> (raw)

We need to add a special post build step to u-boot for our machine.

This step consists of a concatenation of the built u-boot binary to
another (fix) binary and after this running a tool on the resulting
file.

The fix prefix file and the tool are built using another autotools
based (native-)recipe and are installed to the related datadir
resp. bindir.

My idea is to extended the u-boot recipe something like this:

DEPENDS_hipox += " specialtool-native "

do_deploy_append_hipox () {
	cat FOO/usr/share/specialtool/prefixfile ${DEPLOY_DIR_IMAGE}/BAR > ${DEPLOY_DIR_IMAGE}/BAR.wrapped
	specialtool ${DEPLOY_DIR_IMAGE}/BAR.wrapped
}

Is this the right way to do this?

If yes, what is the correct replacement for FOO and BAR?

Steffen




                 reply	other threads:[~2010-04-30 13:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4BDADC9F.9000406@dresearch.de \
    --to=sledz@dresearch.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox