What determines the build location "OE_DIR/tmp/work/*" ?

What determines the build location "OE_DIR/tmp/work/*" ?

[Ulf Samuelsson]

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

Re: What determines the build location "OE_DIR/tmp/work/*" ?

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 993 bytes --]

On Fri, Jan 18, 2013 at 10:30:01PM +0100, Ulf Samuelsson wrote:
> 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.

PACKAGE_ARCH = "${MACHINE_ARCH}"

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]