[oe] Building multiple gdb-cross targets

[Stelios Koroneos]

I think you are missing the point

"bare-metal" gdb does not have any bindings with
glibc/uclibc/eglibc/whatever-libc because its (usually) used to build a
system with no OS (standalone apps).
You also need a "bare-metal" toolchain i.e toolchain that generates code
that can run on the board without any OS (this was the case in most embedded
designs before linux become "embedded")


Stelios S. Koroneos

Digital OPSiS - Embedded Intelligence
http://www.digital-opsis.com
 

> -----Original Message-----
> From: openembedded-devel-bounces at openembedded.org 
> [mailto:openembedded-devel-bounces at openembedded.org] On 
> Behalf Of Geoffrey Wossum
> Sent: Monday, April 07, 2008 5:54 PM
> To: openembedded-devel at openembedded.org
> Subject: Re: [oe] Building multiple gdb-cross targets
> 
> On Friday 04 April 2008 01:46:08 pm Geoffrey Wossum wrote:
> 
> > It was easy enough to build the bare metal debugger outside 
> OE.  Just 
> > seems like you should be able to build this with OE, too.  It seems 
> > like it might need a separate .bb file to pull it off.  Not exactly 
> > sure how you'd force bitbake to use a different target 
> setting.  Maybe 
> > setting the TARGET_OS to be blank in the bitbake file?
> 
> Copied gdb-cross_x.x.bb to gdb-baremetal_x.x.bb.  Added a line:
> TARGET_SYS_avr32 = "avr32"
> 
> That actually seemed to work.
> 
> ---
> Geoffrey
> 
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>