> I have been looking at the include files that you have on your website,
and
> am having a problem getting a handle on how your pre-processor handles
them.
> What do you use for a pre-processor

PREPIC.EXE, which is something we created to work around deficiencies in the
MPASM/MPLINK combination.  The preprocessor is also invoked automatically
when ASMPIC, our MPASM wrapper, assembles a .ASPIC file as apposed to a .ASM
file.

> and how does it determine which of the files it should use?

It doesn't determine, the build system does.  However, we always use the
preprocessor on all PIC assembler source code.  That's why all our source
code file names end in .ASPIC and not in .ASM.

I've updated the web site to include the four build tool executables and
their doc files.  See the new section "PIC Assembler Build Tools" at
http://www.embedinc.com/pic


********************************************************************
Olin Lathrop, embedded systems consultant in Littleton Massachusetts
(978) 742-9014, olin@embedinc.com, http://www.embedinc.com

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.