> I am playing around with MPLAB trying to adjust the environment to my
needs
> and I found kind of strange behavior associated with including the .inc
> files.
>
> In MPLAB's project settings there is a place for defining "Include path".
It
> doesn't seem to work.
>
> I think, that "including" files is a feature of assembler rather then IDE.
>
> Regarding include directive MPASM manual states as follows:
> "If a fully qualified path is specified, only that path will be searched.
> Otherwise, the search order is: current working directory, source file
> directory, MPASM executable directory."
>
> Does it mean that I can't specify my "include directory"?
>
> Am I forced to keep my macro definitions in "MPASM executable directory"
to
> share them among different projects?
>
> 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.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

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