Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3 of 4 RFC] manual: add section about depending on toolchain options
Date: Thu, 19 Sep 2013 16:52:46 +0200	[thread overview]
Message-ID: <20130919165246.687cbe8b@skate> (raw)
In-Reply-To: <CAAXf6LXtiSyVejwF_ZyW3qjzy8CS_n+0Xgj84MGFa-6kk+MggA@mail.gmail.com>

Dear Thomas De Schampheleire,

On Thu, 19 Sep 2013 09:23:37 +0200, Thomas De Schampheleire wrote:

> Well, I think this depends on the semantics of PREFER_STATIC_LIB or
> the way we will handle the dynamic library option(s) in the future. If
> there is really an option that says 'I want static libs', then I think
> it makes sense to add a comment, because it's a user choice. If the
> linking is only based on the architecture supporting it or not, and
> the user will get dynamic libs when supported, then a comment is not
> needed.
> 
> Based on the discussion so far, I don't think we should try to fix the
> situation in the context of this patchset, but rather in a separate
> one. I would therefore propose, for this patchset, to keep the current
> situation and the documentation as proposed in the patch. Later, any
> needed changes can be made when the dynamic library handling is
> cleared out. In the mean time, I will not add new comments for
> packages that depend on !STATIC but do not yet have a comment, as this
> may be wasted effort.
> 
> What do you think?

I fully agree.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-09-19 14:52 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
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 [this message]
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=20130919165246.687cbe8b@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