From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2 of 3 v2] manual: add section about depending on target and toolchain options
Date: Thu, 3 Oct 2013 13:21:24 +0200 [thread overview]
Message-ID: <20131003132124.33f8e945@skate> (raw)
In-Reply-To: <524D50D0.8060906@mind.be>
Dear Arnout Vandecappelle,
On Thu, 03 Oct 2013 13:11:12 +0200, Arnout Vandecappelle wrote:
> The dynamic library support is anyway a bit of a problem, because
> it bears little relation to the config option "prefer static
> libraries". That part, however, will hopefully be fixed when the
> other Thomas adds the choice between static-only, dynamic-only and
> both.
I have patches that do this, they need a bit more testing, but I should
probably send them as a RFC.
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-03 11:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 8:56 [Buildroot] [PATCH 0 of 3 v2] Unification of comments on toolchain option dependencies Thomas De Schampheleire
2013-09-25 8:56 ` [Buildroot] [PATCH 1 of 3 v2] trivial: manual: fix typo formating --> formatting Thomas De Schampheleire
2013-09-25 9:05 ` Samuel Martin
2013-10-06 19:48 ` Peter Korsgaard
2013-09-25 8:56 ` [Buildroot] [PATCH 2 of 3 v2] manual: add section about depending on target and toolchain options Thomas De Schampheleire
2013-10-03 5:30 ` Arnout Vandecappelle
2013-10-03 7:34 ` Thomas De Schampheleire
2013-10-03 11:11 ` Arnout Vandecappelle
2013-10-03 11:15 ` Gustavo Zacarias
2013-10-03 11:21 ` Thomas Petazzoni [this message]
2013-09-25 8:56 ` [Buildroot] [PATCH 3 of 3 v2] Config.in files: unify comments of toolchain option dependencies Thomas De Schampheleire
2013-10-02 20:08 ` [Buildroot] [PATCH 0 of 3 v2] Unification of comments on " Thomas De Schampheleire
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=20131003132124.33f8e945@skate \
--to=thomas.petazzoni@free-electrons.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