Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ashwin Bihari <abihari@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] using the buildroot toolchain
Date: Wed, 8 Nov 2006 09:56:42 -0500	[thread overview]
Message-ID: <1f11a5490611080656l5aa199bdk96417ee32ddb2ada@mail.gmail.com> (raw)
In-Reply-To: <4551E847.60606@olografix.org>

On 11/8/06, Mircha Emanuel `ryuujin` D'Angelo <ryuujin@olografix.org> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all,
> this is my first post here :)
>
> I built a rootfs using buildroot and it works fine :).
>
> Now, I have to build my own applications and I'm wondering how can I use
> the toolchain created with buildroot.
>
> I know I have the toolchain in {$BUILDROOT}/build_{$arch}/staging_dir/
> but I don't know how I can compile other applications with uClibc.
>
> For example, if I wanna build A-0.0. I export the toolchain path, then I
> go in A-0.0 directory.
>
> And now? I would have to do ./configure, but there is bad cause the
> script is looking on my host and not on my toolchain. I can't chroot in
> toolchain path cause I don't have make and other utility.
>
> I hope someone could explain me... :)
>
> thanks all
> mircha
>
> PS: sorry for my english
>

Mircha,

This isn't as much a Buildroot issue as the usage of cross compiler. Anyway,
what you would do is add the location of the cross compiler to the PATH as
you have. Then when you want to "./configure" your appliation, you should
make sure that you add "--target=<arch>" which will make the application
realize it's been cross compiled and will try to look for the compiler.

Regards

-- 
~ Ashwin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20061108/33999575/attachment.html 

  reply	other threads:[~2006-11-08 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 14:23 [Buildroot] using the buildroot toolchain Mircha Emanuel `ryuujin` D'Angelo
2006-11-08 14:56 ` Ashwin Bihari [this message]
2006-11-17 16:09   ` Bernhard Fischer

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=1f11a5490611080656l5aa199bdk96417ee32ddb2ada@mail.gmail.com \
    --to=abihari@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox