All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Moore <will.moore@beraninstruments.com>
To: buildroot@busybox.net
Subject: [Buildroot] Using gcc after builing
Date: Thu, 14 Jan 2010 12:26:01 -0000	[thread overview]
Message-ID: <43758337C78F41CA9E8C64460C150FEF@AP366> (raw)
In-Reply-To: <001501ca9510$d4abba80$7e032f80$@com>

> -----Original Message-----
> From: buildroot-bounces at busybox.net [mailto:buildroot-bounces at busybox.net]
> On Behalf Of Barry Bridges
> Sent: 14 January 2010 11:58
> To: buildroot at busybox.net
> Subject: [Buildroot] Using gcc after builing
> 
> Hi all,
> 
> Sorry in advance for being a bit of a nube here, just finding my feet.
> 
> I have make my build for my arm AT91SAM9263ek without a problem. Many
> thanks to the guys who put all the effort in here to make it so much
> easier to build these things.
> 
> Anyway, i now want to compile my application for the board. Buildroot
> makes the 'correct' version if cross compiler for the device/platform.
> Should i be using this for my application.
> 

Yes.

> If so how do i access it\install it.

See the Buildroot documentation for either the latest stable release 2009.11
or GIT head http://buildroot.uclibc.org/docs.html .
This has some info on using the toolchain built by Buildroot, e.g.
http://buildroot.uclibc.org/downloads/buildroot.html#using_toolchain .

> 
> If not, what should i use and any ideas where is get if from?
> 
> 
> 
> Many thanks
> 
> 
> 
> Barry

      reply	other threads:[~2010-01-14 12:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-14 11:58 [Buildroot] Using gcc after builing Barry Bridges
2010-01-14 12:26 ` Will Moore [this message]

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=43758337C78F41CA9E8C64460C150FEF@AP366 \
    --to=will.moore@beraninstruments.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.