Alan B. Pearce wrote :

> Have a look at Olin's development environment. As each file
> is assembled the .o file is added to a library for the linker to use.

Maybe if used out-of-the-box. I made a few minor changes
to the build scripts (BAT-files), so I link the EXE directly from
the .o files. I added a "make" tool instead, so just the needed
modules are re-assembled each time.

> I  haven't checked the
> MPLINK documentation to see if this is necessary,...

Well, it isn't  :-)

And MPLINK can mix .o and .lib files in the same run,
if you want. This is normal, IMHO, since you often have a
"main" module that is linked from the .o file, and (if you
use that) some LIB files.

And as a final note, using LIB's is just an administrative
thing, it's no difference to the linker AFAIK, between linking
from the plain .o files and building from a LIB.

Jan-Erik.

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads