Unlike PC linkers which now support procedure level granularity in linking,
MPLIB/MPLINK are granular only at the individual object file level.

In other words, all the code that is in one .asm file will end up in one
object file. If placed in a library (possibly with other object files) it
will be included or excluded from the link as a whole. Any reference to any
symbol defined in the module will cause the entire module to be included.

If you want more granularity, you need to write more separate .asm files.

Bob Ammerman
RAm Systems


----- Original Message ----- 
From: "Jan-Erik Soderholm" <jan-erik.soderholm@telia.com>
To: <piclist@mit.edu>
Sent: Wednesday, September 22, 2004 3:00 PM
Subject: RE: [PIC]: Using MPLIB


> Digiled dot com wrote :
>
> > Hello piclisters,
> >       Anyone using MPLIB ??
> >
>
> First, have you checked what the documentation has to say
> about you questions ?
>
> Anyway...
>
> >       Is it possible to include multiple library functions in ONE
> >       library file (.lib)?
>
> One object file (.o)can have multiple "functions" or
> "code sections".
> One library file (.lib) can have multiple object files.
>
> >       Does mplib have porcedure markers (like PROC and ENDP) ?
>
> I'm not sure there are anything called "procedure markers" at all.
> What do you mean with that ? Maybe "code sections". They are defined
> in the ASM source code, not when using/executing MPLIB.
>
> Download and read the document :
>
> "MPASM Assembler User's Guide with MPLINK Object Linker and MPLIB",
> http://ww1.microchip.com/downloads/en/DeviceDoc/33014g.pdf
>
> Best Regards,
> Jan-Erik.
>
> _______________________________________________
> http://www.piclist.com
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist

_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist