[m-dev.] [ddw at miscrit.be: mmc vs a_mmc vs mumc]

[Dominique de Waleffe]

> > first argument. ie:
> > 	mdb     = mercury debug
> > 	mgnuc   = mercury c_compile
> > 	ml      = mercury link
> > 	mprof   = mercury profile
> > 	mmc     = mercury compile
>
> This would be easy and fine on Unix based systems, but process creation
> takes a long time under Windows.
>
> We would have to be very careful not to create any extra processes while
> running these commands (which I guess is quite possible if you just
> source the file rather than executing it).

I second the idea of having one driver which calls the other components of
the system.
Regarding process creation, there are already so many processes created by
all the levels of make and shell that one more or one less wont make much of
a difference.....

I'd like to see someone write a compilation manager (like CM for SML) that
would know about all the complex rules of building a mercury app and
orchestrate the build with just one level of subprocesses under
it....mercury_compile, C compiler, linker...

D.

--------------------------------------------------------------------------
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
--------------------------------------------------------------------------