[m-dev.] Can someone tell me what the -I flag does for mmc?

[Simon Taylor]

On 26-Nov-2004, Ralph Becket <rafe at cs.mu.OZ.AU> wrote:
> The documentation for -I in the users' manual states:
> 
>    -I dir
>    --search-directory dir
>           Append dir to the list of directories to be searched for  
>           imported modules.
> 
> But if I try `mmc --make b -I dir_a' where a.m lives in dir_a, the
> compiler reports that it can't find the source code for module a.

The compiler doesn't search for source code in other directories.
This is usually the wrong thing to do, for example you don't
want to be building interface files for the library in the
compiler directory.

> So clearly -I doesn't do what I thought it did.  Can anybody tell
> me (a) what -I does and (b) whether it is indeed possible to have
> .m files in different directories and have them build using a
> single invocation of mmc?

Try running `mmc -f dir_a/a.m b.m' first before `mmc --make'.

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