From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Passing arguments to the linker when external toolchain is used.
Date: Sun, 25 Nov 2012 23:25:37 +0100 [thread overview]
Message-ID: <50B29AE1.1000100@mind.be> (raw)
In-Reply-To: <CAMJ=MEcBJR8R_2SsfuLSz1dxheVz-iede6R6wG-xd7RvxAdpTQ@mail.gmail.com>
On 25/11/12 21:56, Ronny Meeus wrote:
> On Sun, Nov 25, 2012 at 9:44 PM, Arnout Vandecappelle<arnout@mind.be> wrote:
[snip]
>> In that case, why not just pass them with LDFLAGS?
>>
>
> Our SW is build in 2 parts: the Linux kernel, buildroot and other
> components are build via buildroot itself.
> Next to this we also have other applications that we build in with "a
> private build infrastructure" using the toolchain, include files etc
> of buildroot.
>
> By adding the extra linker parameters with the wrapper construction we
> can transparantly introduce a new toolchain (with the required
> parameters) in that environment without impact on our build
> infrastructure. The big advantage is that the complete toolchain
> selection (CPU,ABI etc) only needs to be done in buildroot.
Yes, sounds like a valid use case.
I also expect that the LDFLAGS are not passed reliably for all packages:
they are hardly ever used, and there are no autobuilder configurations with
any LDFLAGS, so errors in passing LDFLAGS can go unnoticed.
I don't think we have any other architecture currently in buildroot that
requires something to be passed to ld. If this wrapper construction is
added to buildroot, it would be good if we would also have an internal
use case.
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-11-25 22:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 13:04 [Buildroot] Passing arguments to the linker when external toolchain is used Ronny Meeus
2012-11-24 23:33 ` Arnout Vandecappelle
2012-11-25 17:23 ` Ronny Meeus
2012-11-25 20:44 ` Arnout Vandecappelle
2012-11-25 20:56 ` Ronny Meeus
2012-11-25 22:25 ` Arnout Vandecappelle [this message]
2012-11-26 20:45 ` Ronny Meeus
2012-11-26 22:33 ` Arnout Vandecappelle
2012-11-28 19:38 ` Ronny Meeus
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=50B29AE1.1000100@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