Re: compiling a native (x86) application using Yocto

[Denys Dmytriyenko <denys@ti.com>]

Sajesh,

It appears your Makefile directly calls native gcc to produce x86 binary.

Now, BBCLASSEXTEND allows you to "extend" a regular target recipe that 
produces an ARM binary to also produce a native x86 binary. Naming your recipe 
as something-native.bb doesn't change the procedure.

So, it first builds and strips an ARM binary and then would have done the same 
for x86 binary. But since you set GCC=gcc in your Makefile, it chokes on the 
ARM-stripping step.

Now, if you only want a native recipe, instead of BBCLASSEXTEND, you should 
just do "inherit native" and that class would short-circuit all the target 
build and strip tasks.

-- 
Denys


On Thu, Jul 25, 2013 at 04:30:07PM -0400, Saran, Sajesh Kumar wrote:
> Recipe is attached with the mail.
> 
> Regards,
> Sajesh
> 
> -----Original Message-----
> From: Dmytriyenko, Denys 
> Sent: Thursday, July 25, 2013 4:25 PM
> To: Saran, Sajesh Kumar
> Cc: meta-arago@arago-project.org
> Subject: Re: [meta-arago] compiling a native (x86) application using Yocto
> 
> On Wed, Jul 24, 2013 at 06:26:48PM +0000, Saran, Sajesh Kumar wrote:
> > Hi,
> > 
> > I am trying to compile a native tool/application using Yocto.
> > 
> > I have added BBCLASSEXTEND = "native" to the recipe. The compilation 
> > goes thru fine. But, in do_package_qa it is running a strip command 
> > using arm-linux-gnueabihf-strip, which is failing because the 
> > application is compiled using gcc. Do I have to anything else to fix of this issue?
> 
> Strange, that should be enough... Care to share the recipe?
> 
> --
> Denys