From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3 of 4 RFC] manual: add section about depending on toolchain options
Date: Wed, 18 Sep 2013 23:57:41 +0200 [thread overview]
Message-ID: <523A21D5.6040005@mind.be> (raw)
In-Reply-To: <20130918201812.3e08d883@skate>
On 18/09/13 20:18, Thomas Petazzoni wrote:
> Dear Gustavo Zacarias,
>
> On Wed, 18 Sep 2013 15:05:23 -0300, Gustavo Zacarias wrote:
>> On 09/18/2013 02:59 PM, Thomas Petazzoni wrote:
>>
>>> I think it's a bit more than just renaming this symbol. I can try to
>>> cook something.
>>
>> Add the relevant legacy entry, adjusting help / manuals.
>> Is there something else i'm missing?
>
> Yes, we probably want to have the choice between building static only,
> static + shared, or shared only, default to shared only. Currently,
> when !BR2_PREFER_STATIC_LIB, we build both the shared and static
> variants, which takes time because it requires building everything
> twice, once with -fPIC, once without.
I don't think the static + shared option really makes sense, does it?
The only use case I can think of is when you want a proprietary
executable to link statically in order to speed up start time.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
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:[~2013-09-18 21:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 9:01 [Buildroot] [PATCH 0 of 4 RFC] Unification of comments on toolchain option dependencies Thomas De Schampheleire
2013-09-18 9:01 ` [Buildroot] [PATCH 1 of 4 RFC] trivial: manual: fix grammar of 'to express' Thomas De Schampheleire
2013-09-18 14:33 ` Peter Korsgaard
2013-09-18 9:01 ` [Buildroot] [PATCH 2 of 4 RFC] trivial: manual: multimedia is no longer a subdirectory Thomas De Schampheleire
2013-09-18 14:33 ` Peter Korsgaard
2013-09-18 9:01 ` [Buildroot] [PATCH 3 of 4 RFC] manual: add section about depending on toolchain options Thomas De Schampheleire
2013-09-18 11:15 ` Thomas De Schampheleire
2013-09-18 14:34 ` Peter Korsgaard
2013-09-18 16:34 ` Thomas Petazzoni
2013-09-18 17:30 ` Thomas De Schampheleire
2013-09-18 17:40 ` Thomas Petazzoni
2013-09-18 17:46 ` Gustavo Zacarias
2013-09-18 17:59 ` Thomas Petazzoni
2013-09-18 18:05 ` Gustavo Zacarias
2013-09-18 18:18 ` Thomas Petazzoni
2013-09-18 21:57 ` Arnout Vandecappelle [this message]
2013-09-19 4:10 ` Thomas Petazzoni
2013-09-19 19:06 ` Arnout Vandecappelle
2013-09-18 22:06 ` Arnout Vandecappelle
2013-09-19 7:23 ` Thomas De Schampheleire
2013-09-19 14:52 ` Thomas Petazzoni
2013-09-19 19:07 ` Arnout Vandecappelle
2013-09-18 9:01 ` [Buildroot] [PATCH 4 of 4 RFC] Config.in files: unify comments of toolchain option dependencies Thomas De Schampheleire
2013-09-19 10:57 ` Thomas De Schampheleire
2013-09-19 11:47 ` Samuel Martin
2013-09-19 14:54 ` 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=523A21D5.6040005@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