All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 19 Sep 2013 21:07:42 +0200	[thread overview]
Message-ID: <523B4B7E.9070204@mind.be> (raw)
In-Reply-To: <CAAXf6LXtiSyVejwF_ZyW3qjzy8CS_n+0Xgj84MGFa-6kk+MggA@mail.gmail.com>

On 19/09/13 09:23, Thomas De Schampheleire wrote:
> Arnout, all,
>
> On Thu, Sep 19, 2013 at 12:06 AM, Arnout Vandecappelle <arnout@mind.be> wrote:
> [..]
>>
>>   For the 'dynamic library' option, I don't think it's that important to add
>> a comment for it. It's so exotic, and you probably select only very few
>> packages in that case anyway, so the likelihood of someone encountering that
>> situation is pretty slim.
>>
>
> 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?

  Good idea.

  Regards,
  Arnout

[snip]


-- 
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

  parent reply	other threads:[~2013-09-19 19:07 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
2013-09-19 19:07       ` Arnout Vandecappelle [this message]
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=523B4B7E.9070204@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.