From: Claus Klein <claus.klein@arcormail.de>
To: buildroot@busybox.net
Subject: [Buildroot] Boost package settings for using cross-compiler ?
Date: Tue, 21 Nov 2006 21:12:22 +0100 [thread overview]
Message-ID: <200611212112.23510.claus.klein@arcormail.de> (raw)
In-Reply-To: <loom.20061120T163936-97@post.gmane.org>
Hi,
we use boost with ppc crosscompiler, here is my buildroot package.
Sure, its depend an bjam installed on host, the buildroot C++ toolchain, theading, zlib, ....
Realy, a big package for an embedded device ;-)
Check the boost configuration in boost.mk!
Regards,
claus
On Monday 20 November 2006 16:46, MikeW wrote:
> I successfully (so I thought) created a package file for building the Boost C++
> libraries under buildroot, but when I came to use them, found they had been
> built using native (i386) tools, unlike the rest of the libraries built
> by Buildroot, which were ARM architecture.
>
> The top-level Boost config parameters do not appear to have a tool
> prefix or macro to support cross-tools.
>
> So - has anyone built Boost successfully before ?
>
> I imagine that if so, the distribution would already contain
> a package file for the library ...
>
> Regards,
> Mike
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: boost.tgz
Type: application/x-tgz
Size: 2544 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20061121/3ab5b92a/attachment.bin
next prev parent reply other threads:[~2006-11-21 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 15:46 [Buildroot] Boost package settings for using cross-compiler ? MikeW
2006-11-21 20:12 ` Claus Klein [this message]
2006-11-22 8:55 ` MikeW
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=200611212112.23510.claus.klein@arcormail.de \
--to=claus.klein@arcormail.de \
--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