[m-dev.] Problematic Mmake dependencies

[Fergus Henderson]

On 06-Jul-1999, Warwick Harvey <wharvey at cs.monash.edu.au> wrote:
[...]
> So any scheme which has all the automatically generated variable and rule 
> definitions (i.e. what's in the `.dep' file now) before all the 
> user-specified variable definitions (from the Mmakefile) cannot 
> automatically add per-file dependencies based on user-defined variables.
> 
> :-(
> 
> (Just for the record, the problem is how to add .init file [and library 
> file] dependencies automatically, based on variables set in the user's 
> Mmakefile --- with the caveat that it should take into account any per-file 
> definitions.)
> 
> Of the two "splitting" options discussed last time, I think the (physical) 
> splitting of the `.dep' file is the better one.  It's only one extra file 
> per primary target (executable, library, whatever), and probably (?) 
> requires less of a performance hit every time mmake is invoked.

Yes.  Given that the number of primary targets is usually pretty small,
I think that the cost of an extra file per primary target is acceptable.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>  |  of excellence is a lethal habit"
PGP: finger fjh at 128.250.37.3        |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------