[Buildroot] using the buildroot toolchain

[Buildroot] using the buildroot toolchain

[Mircha Emanuel `ryuujin` D'Angelo]

-----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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFFUehH0CI10whGevwRAmgHAJwLfEstwIbypDPD0hJrYimzxLb2/gCdGdWr
jfsqkcduyj0cSQS7/TGu6bQ=
=+TyE
-----END PGP SIGNATURE-----

[Buildroot] using the buildroot toolchain

[Ashwin Bihari]

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 

[Buildroot] using the buildroot toolchain

[Bernhard Fischer]

On Wed, Nov 08, 2006 at 09:56:42AM -0500, Ashwin Bihari wrote:
>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.

If you want to use a native compiler on your target (as opposed to a
cross-compiler on your host) then go to "packages" and select "native
toolchain in the target filesystem" (== BR2_PACKAGE_GCC_TARGET=y)