[Gm2] Re: do I need separate libfiles for every module?

[john o goyo]

On 6-Jan-10, at 7:06 AM, Gaius Mulley wrote:

> Martin Kalbfuß <address@hidden> writes:
> [...]
>
> > When I work with C and gcc, it's completely up to me where the  
> > code is,
> > as long as I link it
>
> ok.  Sure this is true - gm2 could be altered to work in the same way.
> Perhaps it should check for .o files first of all and if they do not
> exist continue by looking for .a files and lastly add in the -llibs
> and pass the whole collection to gcc for the link.  We would get
> slightly less helpful error messages at link time if it fails but it
> would match the gcc behaviour.

> [...]
>
> true - it can be altered to match this behaviour..  The main point of
> difference is that gm2 will build the list of objects necessary for
> linking from the module imports.  But it could be altered so that it
> does not insist on these being present

This does beg the question of what do with pre-compiled libraries?   
It is
not unusual to have a library archive contain pre-compiled modules of
some subsystem and then link against that library with only the  
defintion
modules exposed (so to speak).

john