Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: gdb@sourceware.org
Subject: Re: Automatic dependency tracking
Date: Fri, 27 Jun 2008 14:30:00 -0000	[thread overview]
Message-ID: <m3y74rlzlo.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4864BF63.5010904@st.com> (Andrew STUBBS's message of "Fri\, 27 Jun 2008 11\:22\:27 +0100")

[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]

[ I'm re-sending this, this time w/ an attachment, since sourceware
rejected the original note as too big... Andrew, sorry if you get this
twice. ]

>>>>> "Andrew" == Andrew STUBBS <andrew.stubbs@st.com> writes:

Andrew> OK, I understand now. Presumably it would still be possible to retain
Andrew> non-GNU make compatibility for build-only purposes by also providing a
Andrew> regular dependency - basically just removing the bar from the above - 
Andrew> and then preprocessing the Makefile, like AM_CONDITIONAL?

Yeah, probably.  Or someone could redo the Makefile in Automake, which
automates all this.

I can't emphasize enough how much nicer it is to assume GNU make than
to try to be portable.

Andrew> Auto dependency tracking would be very nice to have though. :)

I've appended a patch to do it.  I made this against the python
repository on gitorious -- but aside from the extra code for the
python objects, it would be the same for the trunk.  The patch is
nearly all deletions.

Give it a whirl & let me know what you think.  No ChangeLog entry yet,
sorry.

Tom


[-- Attachment #2: the patch --]
[-- Type: application/x-gzip, Size: 20587 bytes --]

  parent reply	other threads:[~2008-06-27 14:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200806152203.14626.pedro@codesourcery.com>
     [not found] ` <u3anel69s.fsf@gnu.org>
     [not found]   ` <20080616012617.GA8944@caradoc.them.org>
     [not found]     ` <g35201$2uf$2@ger.gmane.org>
     [not found]       ` <m33an413yx.fsf@fleche.redhat.com>
2008-06-25 18:29         ` Daniel Jacobowitz
2008-06-25 19:30           ` Andreas Schwab
2008-06-25 21:35           ` Stan Shebs
2008-06-26  0:08           ` Tom Tromey
2008-06-26  1:47           ` Joel Brobecker
2008-06-26  9:48           ` Andrew STUBBS
2008-06-26 17:30             ` Tom Tromey
2008-06-27 10:23               ` Andrew STUBBS
2008-06-27 14:03                 ` Daniel Jacobowitz
2008-06-27 16:09                   ` Andrew STUBBS
2008-06-27 14:30                 ` Tom Tromey [this message]
2008-06-28 19:20           ` Mark Kettenis
2008-06-28 19:31             ` Tom Tromey
2008-06-29 14:47               ` Daniel Jacobowitz
2008-06-29 15:36               ` Tom Tromey
2008-06-29 16:26                 ` Tom Tromey
2008-06-29 14:42             ` Daniel Jacobowitz

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=m3y74rlzlo.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=andrew.stubbs@st.com \
    --cc=gdb@sourceware.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