Re: non-recursive build question

[Noel Yap]

sandy currier wrote:
> A recursive build design trick that I have seen before and am now
> dealing with is where a bunch of work (target commands are being
> executed) is done only to find that the target is not actually modified.
> One example of this is generating a export list of symbols for a
> shared library.  Specifically, even though the object files that
> go into a shared library have changed, possibly quite so, the
> 'external' symbol list including all argument specifications (ansi C)
> has not.

Upon re-reading this part, I see that order rules won't solve the problem.

Noel