Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Prepare to handle more than two toolchain types
Date: Fri, 26 Mar 2010 20:46:31 +0100	[thread overview]
Message-ID: <20100326194619.8693.69302.stgit@roazhon.bzh.lan> (raw)

To prepare to handle more than two toolchian types, we should always
explicitly check the configured toolchain type, rather than falling
back to the non-selected one.

As this is a choice, we are sure that either the 'buildroot' or the
'external' toolchain is seleted, so we do not have to handle the
default case (both/none selected).

---

Yann E. MORIN (1):
      toolchain: prepare for more than two alternatives


 Makefile                   |    6 +++---
 package/Makefile.in        |   11 +++++------
 package/gettext/gettext.mk |    2 +-
 3 files changed, 9 insertions(+), 10 deletions(-)

--
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

             reply	other threads:[~2010-03-26 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-26 19:46 Yann E. MORIN [this message]
2010-03-26 19:46 ` [Buildroot] [PATCH] toolchain: prepare for more than two alternatives Yann E. MORIN
2010-03-26 20:34   ` Thomas Petazzoni
2010-03-31  8:53   ` Peter Korsgaard

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=20100326194619.8693.69302.stgit@roazhon.bzh.lan \
    --to=yann.morin.1998@anciens.enib.fr \
    --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