On Wed, 26 Jun 2002, Olin Lathrop wrote:

>> How do you maintain your macros library?
>
>I don't remember the details now, but I seem to recall some problems with
>MPASM and include path also.  Keep in mind tha MPASM is really a fossilized
>DOS program dressed up for Windows.  It only handles 8.3 file names.  Yes,
>this is stupid and very annoying.
>
>I keep an extensive set of "standard" include files, and arrange the
>directory structure so that the my include directory is always ..\pic when
>doing a build.  This is not a great answer, but it does work.  You can
>download our PIC build environment with tools and build scripts that
>incorporate these assumptions by starting at http://www.embedinc.com/pic.

After a number of adventures (that began in about 1995, when I first built
a programmer and used the PIC16C54), I have come to copy the header file
of the currently used PIC into the project directory and make SURE that I
am using *that* include file, and no other, for that project. This has
meant and still means some forced includes overriding defaults in C
compilers and assemblers so far. Changing all EQUs to SETs in default
include files helps here (use a script, like sed, to do this)... It also
means that I can still assemble code written in 1995 ...

Peter

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics