public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Ian Roxborough <irox@redhat.com>
To: leonp@plris.com
Cc: sourcenav@sourceware.cygnus.com
Subject: Re: Include tree question
Date: Wed, 04 Apr 2001 11:06:00 -0000	[thread overview]
Message-ID: <3ACB623F.B7491AA6@redhat.com> (raw)
In-Reply-To: <5.0.2.1.0.20010404121248.00a71e68@plris.com>

leonp@plris.com wrote:
> 
> Hello,
>          In my project I have one include file a.h which includes another
> file b.h. In the Makefile generated by SN 5.0 I see the *.c file dependency
> on a.h but no references to b.h Thus any changes made to b.h are
> "invisible" for make utility.
>          Is this a bug or some kind of my problem?

Yeah, this is a bug.  Well, a limitation, when generating
the dependencies, basically it doesn't recurs the dependencies
of dependencies (just that of the source file).

I'm not sure when this will be fixed, I'm currently looking at
doing a bunch of work on build system to make it more complete
and flexible.

Ian.

  reply	other threads:[~2001-04-04 11:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-04  5:52 leonp
2001-04-04 11:06 ` Ian Roxborough [this message]
2001-04-04 13:17   ` 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=3ACB623F.B7491AA6@redhat.com \
    --to=irox@redhat.com \
    --cc=leonp@plris.com \
    --cc=sourcenav@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).