Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: vapier@gentoo.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdbserver: start a gitignore
Date: Wed, 22 Dec 2010 11:24:00 -0000	[thread overview]
Message-ID: <E1PVMnq-00047S-4X@fencepost.gnu.org> (raw)
In-Reply-To: <20101222044518.GJ2596@adacore.com> (message from Joel Brobecker	on Wed, 22 Dec 2010 08:45:18 +0400)

> Date: Wed, 22 Dec 2010 08:45:18 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> I'm OK but slightly hesitant to introduce a .gitignore for files that
> are compilation artifacts, not development artifacts.  If we start
> on that road, the list is possibly quite long.

How long can it be?  Something like *.o, *.so, *.exe, and a couple of
binaries we produce?  Is that really a problem?

I see such exclusions in every GNU project I'm working on.  I don't
think this road is too long ;-)

> I believe that we should encourage people to compile GDB using
> a build directory that is different from the source directory.

Right, but you cannot (and shouldn't, IMO) force people doing that by
such measures.  People who want to build in the source tree will
complain, but will not stop doing that.

> Except I don't know why I think that! :-).

I do.  From gdb/README:

  You can build GDB right in the source directory:

	cd gdb-VERSION
	./configure
	make
	cp gdb/gdb /usr/local/bin/gdb     (or wherever you want)

  However, we recommend that an empty directory be used instead.
  This way you do not clutter your source tree with binary files
  and will be able to create different builds with different 
  configuration options.


  parent reply	other threads:[~2010-12-22 11:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15 12:33 Mike Frysinger
2010-12-22  4:45 ` Joel Brobecker
2010-12-22  5:32   ` Yao Qi
2010-12-22 11:24   ` Eli Zaretskii [this message]
2010-12-22 14:43     ` Joel Brobecker
2010-12-22 18:17     ` Mike Frysinger
2010-12-23  4:22       ` Joel Brobecker
2010-12-24  2:55         ` Mike Frysinger
2010-12-22 22:05     ` Michael Snyder
2010-12-23  3:19       ` Mike Frysinger
2010-12-22 15:58   ` Tom Tromey

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=E1PVMnq-00047S-4X@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.org \
    /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