Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Doug Evans <dje@google.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb@sourceware.org
Subject: Re: sim: using automake
Date: Mon, 11 Jul 2011 17:20:00 -0000	[thread overview]
Message-ID: <201107111320.22250.vapier@gentoo.org> (raw)
In-Reply-To: <CADPb22RafAq6iqz2mUTMh=ebA=FO9+QdUO+O4ymuKHfP9bW35A@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 1623 bytes --]

On Monday, July 11, 2011 12:38:13 Doug Evans wrote:
> On Mon, Jul 11, 2011 at 7:57 AM, Tom Tromey <tromey@redhat.com> wrote:
> >>>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:
> > Mike> ive been bit by this multiple times, and it always seemed crazy to
> > Mike> me that we still do manual dependency management.  many of the
> > Mike> other sourceware projects have converted to automake and dropped
> > Mike> the hardcoded lists, so is there anything holding back the sim dir
> > Mike> other than someone doing it ?
> > 
> > It seems like an improvement to me.
> 
> "Well ..."
> I'd rather not make this transition without a bit more discussion.
> [I would prefer to avoid automake.]

much of the sourceware tree has converted.  seems the only major dirs not 
using it are newlib/libgloss/gdb/sim.
$ ls `find -name Makefile.in | sed 's:[.]in:.am:g'`

not saying this means "gdb/sim must convert", just providing more context to 
show that it's inevitable ! :)

> One question and one observation:
> 
> Question: can automake handle dependencies on machine generated files?
> I think(!) the answer is "no", so automake doesn't solve all problems.

i'm not sure what you mean by machine generated files.  could you provide 
specific examples ?

> Observation: gdb no longer manually describes dependencies (*1) yet it
> doesn't use automake.
> 
> ---
> (*1): I realize it's more complicated than that, e.g. source files from
> subdirs.

just having dependency info in the current dir would be a vast improvement.  
i'll poke the gdb system to see how it's doing it.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-07-11 17:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201107080344.p683iRUq024788@ignucius.se.axis.com>
2011-07-08  4:34 ` Mike Frysinger
2011-07-11 14:57   ` Tom Tromey
2011-07-11 16:38     ` Doug Evans
2011-07-11 17:20       ` Mike Frysinger [this message]
2011-07-11 17:25       ` Tom Tromey
2011-07-11 17:42         ` Mike Frysinger
2011-07-11 17:54         ` Doug Evans

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=201107111320.22250.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=dje@google.com \
    --cc=gdb@sourceware.org \
    --cc=tromey@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