Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nathanael Nerode <neroden@doctormoo.dyndns.org>
To: gcc@gcc.gnu.org, gdb@sources.redhat.com, binutils@redhat.com
Subject: new build scheme naming
Date: Sat, 06 Jul 2002 15:07:00 -0000	[thread overview]
Message-ID: <20020706220545.GA15254@doctormoo.dyndns.org> (raw)

This message refers to
http://gcc.gnu.org/ml/gcc/2002-02/msg01816.html
and it may also be useful to look at
http://gcc.gnu.org/ml/gcc/2002-02/msg01842.html

I'd like to start working on the transition sometime soon, but I want to
settle a couple of naming issues first.

* Name for the directory.  'build' is a terrible name (confusion with
the 'build machine') and 'install' isn't much better.  I would promote a
name with the host encoded into it for clear separation of tools which
run on the host from those which run on the target.  How about
${host_alias}/recently_built
${host_alias}-recently_built
${host_alias}/built
${host_alias}-built
${host_alias}/tools
${host_alias}-tools
${host_alias}/preinstall
${host_alias}-preinstall

(and similarly, ${target_alias}/* for target libraries)

Any preferences?  Any better ideas?...

* Variable to use for this directory in 'configure' files and Makefiles;
again, $build_prefix is a very bad choice.
$host_recently_built
$host_built
$host_tools
$host_preinstall_dir

(and similarly $target_* for target libraries)

Any preferences?  Any better ideas?...

--Nathanael


             reply	other threads:[~2002-07-06 22:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-06 15:07 Nathanael Nerode [this message]
2002-07-07 11:52 ` mike stump

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=20020706220545.GA15254@doctormoo.dyndns.org \
    --to=neroden@doctormoo.dyndns.org \
    --cc=binutils@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    /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