From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] cross-cxx support
Date: Mon, 30 Jul 2007 22:39:46 +0200 [thread overview]
Message-ID: <20070730203946.GE29064@aon.at> (raw)
Hi all,
If you want to build lzma for the target, you need a working
cross-compiler for C++.
The patch referenced below does add BR2_GCC_CROSS_* compilers, adds a
variable that points to the auto-generated files that can be used for
dependency-tracking (somebody, i think it was sjhill broke this by
moving the former toplevel "include" dir to
package/config/buildroot-config/*) and adjusts accordingly.
This is just a theory of operation and not yet tested.
Comments (or testers) welcome..
http://uclibc.org/~aldot/buildroot/br2.gcc_cross_cxx.00.diff
cheers,
Bernhard
PS: re: theory. Toggling stuff in (menu)config is supposed to update the
timestamp of the files in BR2_DEPENDS_DIR, so we transparently can
recompile if a prerequisite changes. Other examples would be e.g. LFS
support for both the cross- as well as an eventual target compiler (and
uClibc et al). If the cross-compiler/libc changed, we have to recompile
everything, ultimately.
reply other threads:[~2007-07-30 20:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070730203946.GE29064@aon.at \
--to=rep.dot.nop@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