From: Ulf Samuelsson <openembedded@emagii.com>
To: openembedded-devel@lists.openembedded.org
Subject: What determines the build location "OE_DIR/tmp/work/*" ?
Date: Fri, 18 Jan 2013 22:30:01 +0100 [thread overview]
Message-ID: <50F9BED9.8020504@emagii.com> (raw)
I am building a driver which will load firmware at runtime.
For development purposes, I have defined two machines,
which will be used to build two different versions of the driver.
Have a separate recipe for the firmware.
Each machine defines FW_VERSION which is used to select
a subtree containing the firmware, so the same recipe is used for both
machines.
The driver gets built in "$OE_DIR/tmp/work/<machine>-angstrom-linux/gnueabi"
but the firmware gets built in "$OE_DIR/tmp/work/armv7a-none-linux-gnueabi".
This means that the same tree is used for both machines,
which of course does not work.
Is there a way to define that the recipe should be built in
"$OE_DIR/tmp/work/<machine>-angstrom-linux/gnueabi"?
Otherwise, I guess I have to use two different recipes.
BR
Ulf Samuelsson
next reply other threads:[~2013-01-18 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 21:30 Ulf Samuelsson [this message]
2013-01-18 21:46 ` What determines the build location "OE_DIR/tmp/work/*" ? Martin Jansa
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=50F9BED9.8020504@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox