From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] preparing rootfs with gcc in buildroot
Date: Thu, 21 Jun 2012 22:31:05 +0200 [thread overview]
Message-ID: <4FE38489.8060803@mind.be> (raw)
In-Reply-To: <jrvjm2$sls$1@dough.gmane.org>
On 06/21/12 18:55, Grant Edwards wrote:
> If you want to build things that use libraries that were built as part
> of buildroot, then you have to add a couple more command line options
> to tell the compiler/linker where to find the include and library
> files created by buildroot (e.g.<wherever>/output/target.
And even that is not necessary if you use output/host/usr/bin/xxx-gcc
as the cross-compiler - that one has the sysroot hard-coded.
By the way, you should point to <wherever>/output/staging, not
<wherever>/output/target. target doesn't normally contain header
files or static libraries.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-06-21 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 12:16 [Buildroot] preparing rootfs with gcc in buildroot Kevin Wilson
2012-06-21 12:28 ` Thomas Petazzoni
2012-06-21 16:38 ` Kevin Wilson
2012-06-21 16:55 ` Grant Edwards
2012-06-21 20:31 ` Arnout Vandecappelle [this message]
2012-06-21 21:24 ` Grant Edwards
2012-06-21 21:55 ` Thomas Petazzoni
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=4FE38489.8060803@mind.be \
--to=arnout@mind.be \
--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