Mike Shal wrote: > Unfortunately, what gcc actually does with the .d file (as in, which > directory it gets stored, what it lists as the target, etc) has > changed somewhat drastically between gcc versions (IIRC, between 3.0 > -> 3.3 is pretty wacky). So if you know what gcc version you're > building with it can be pretty simple.
We used to have several variants of rule for doing just that but, in the end, we spent the time to change the core part of the rule so that we could run in the directory where we want the .d file to be created. We were post-processing the .d file anyway, to tidy-up paths to be relative to make variables. That lets us use the same rule for all the gcc variants we use. It works very well for us - I'd certainly add my recommendation to Mike's. ------------------------------------- Martin's Outlook, BlueArc Engineering _______________________________________________ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
