Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/5] toolchain: rename base target for external toolchains
Date: Mon, 19 Jul 2010 17:44:36 -0500	[thread overview]
Message-ID: <201007191744.38170.minimod@morethan.org> (raw)
In-Reply-To: <201007192249.00218.yann.morin.1998@anciens.enib.fr>

On Mon July 19 2010, Yann E. MORIN wrote:
> Mitch, All,
> 
> On Monday 19 July 2010 03:50:54 Mitch Davis wrote:
> > On Tue, Jul 13, 2010 at 6:46 AM, Yann E. MORIN
> > <yann.morin.1998@anciens.enib.fr> wrote:
> > > It is misleeading to name the external toolchain make target 'uclibc', as
> > > external toolchains can be based on other C libraries (eg. glibc or eglibc).
> 
> > I understand your point about uclibc not being a suitable generic
> > name, but I'm not sure toolchain-prepare is the ideal name.  To me,
> > what this target does is guarantees the presence of the C run time
> > library (whether that be uClibc, glibc, etc).  Might "c-rtl" or
> > similar be a better name?  (Of course, in order to generate the RTL,
> > the toolchain will need to be there, as usual).
> 
> OK, I agree that we can drop this patch for now, and do the rename later.
> "c-rtl" is not that descriptive either... Even in-contect, it took me a
> while to see what it meant...
> 
> Maybe smthg like:
> fill-me-that-fscking-staging-and-target-with-the-fscking-runtime-from-toolchain-and-dont-forget-headers-and-statics-for-staging-please-oh-and-build-the-toolchain-if-needed-while-youre-at-it-if-you-dont-care-you-are-such-a-lovely-pet
> 
> Hehe! Yes, I like that one! :-)
> 

This is supposed to be computer science, acronyms only may be applied -

How about:
My-Software, Vital-C, Run-Time. Direct, Digital Loading libraries? 
or which would be MSVCRT.DLL as an acronym?

Something short, sweet and descriptive; such as found in en_OpenSSL:
EXP-EDH-RSA-DES-CBC-SHA
Which, believe it or not, is the plain text version of an acronym used.
Tack a: BR2- on the front of something like that and call it decision made.
;-)

Mike
> [ Thomas, I bet you, this time! :) ]
> 
> > I can also imagine a scenario where one is building such a minimal
> > system that one needs the toolchain, but not the RTL.  What are good
> > target names to guarantee the toolchain, and the RTL, as separate
> > targets?
> 
> Well, it will require some thinking...
> 
> Regards,
> Yann E. MORIN.
> 

  reply	other threads:[~2010-07-19 22:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-12 20:46 [Buildroot] [PATCH 0/5] Preparatory work on toolchains - v3 Yann E. MORIN
2010-07-12 20:46 ` [Buildroot] [PATCH 1/5] toolchain: move helper functions from external toolchain Yann E. MORIN
2010-07-12 20:46 ` [Buildroot] [PATCH 2/5] toolchain: rename external toolchain dir Yann E. MORIN
2010-07-12 20:46 ` [Buildroot] [PATCH 3/5] toolchain: move makefile includes Yann E. MORIN
2010-07-12 20:46 ` [Buildroot] [PATCH 4/5] toolchain: move buildroot config files Yann E. MORIN
2010-07-12 20:46 ` [Buildroot] [PATCH 5/5] toolchain: rename base target for external toolchains Yann E. MORIN
2010-07-19  1:50   ` Mitch Davis
2010-07-19 20:48     ` Yann E. MORIN
2010-07-19 22:44       ` Michael S. Zick [this message]
2010-07-20  0:13       ` Mitch Davis
  -- strict thread matches above, loose matches on Subject: below --
2010-06-25 22:15 [Buildroot] [PATCH 0/5] Preparatory work on toolchains - v2 Yann E. MORIN
2010-06-25 22:15 ` [Buildroot] [PATCH 5/5] toolchain: rename base target for external toolchains Yann E. MORIN
2010-06-27 21:08   ` Peter Korsgaard
2010-06-01 21:52 [Buildroot] [pull request] Preparatory work on toolchains Yann E. MORIN
2010-06-01 21:53 ` [Buildroot] [PATCH 5/5] toolchain: rename base target for external toolchains Yann E. MORIN

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=201007191744.38170.minimod@morethan.org \
    --to=minimod@morethan.org \
    --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