[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Wed, 01 Oct 2003 15:05:47 -0700
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030924 Thunderbird/0.3
When I first looked at the auto-dependency stuff at
http://make.paulandlesley.org/autodep.html, I was pretty excited, but
now I'm not so sure. What I'd really like is this:
In this scenario, foo.h declares a "library" function defined in foo.c.
This function is called in main.c, which includes foo.h. As far as I
know, this is the generally accepted way to modularize things. However,
gcc's dependency generation doesn't trace main.c's dependency on foo.c,
only on foo.h. How can this dependency be known? Or even assumed,
given that there is a corresponding .c file for .h file?
Dynon Avionics, Inc.
[This E-mail scanned for viruses by digiposs.com]
- auto-dependency usefulness?,
Bryce Schober <=