[m-rev.] for review: mmc --make for external foreign files improvements

[Simon Taylor]

On 19-Dec-2002, Peter Ross <pro at missioncriticalit.com> wrote:
> On Thu, Dec 19, 2002 at 04:18:05PM +1100, Simon Taylor wrote:
> > On 18-Dec-2002, Peter Ross <pro at missioncriticalit.com> wrote:
> > > Estimated hours taken: 24
> > > Branches: main
> > > 
> > > Change `mmc --make' so that it no longer builds the external foreign
> > > object files at the same time as it builds the target object file.
> > > 
> > > This allows one to build on the IL backend where building an external
> > > foreign file assembly depends on having all the imported Mercury
> > > assemblies built first.
> > > 
> > > Various fixes were also added so that `mmc --make --grade il' could make
> > > an executable.
> > 
> > > compiler/make.module_target.m:
> > > 	Always create a directory to hold the target file before
> > >	building the target file.
> > 
> > Why?
> > 
> because when building tests/hard_coded/factt.m Mercury/cs isn't created
> and one gets an error.  This happens with the current ROTD.

The bug here is that modules__fact_table_file_name should take
an argument to control whether the directory is created, just
as module_name_to_file_name does.

> It also seems to me that this the is the correct time to ensure that the
> directory exists when building the target file.

It's not, because the directory needs to be created even when
compiling without `mmc --make'.

Simon.
--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------