> Olin, feel free to add this to your environment if you feel it is
useful.
> Just a tiny pay back from me as a thanks for your extremely useful
system
> and macros.

Thanks.  We actually use something just a little above what is released on
the web page.  It's a bit more tangled into our specific environment, so I
don't release it.  I am working on a much grander scheme that will allow
proper tree structured builds, build only if needed, multiple source
versions, and a heirarchy of source "branches" for testing production,
different target environments, etc.  I will probably release this once its
been deployed here for a while, but don't hold your breath waiting for it.
There always seems to be something else to do before working on it.

> @echo off
> rem
> rem   BUILD <.INS.ASPIC file name>
> rem
>
> rem cls
> cd %embedinc%\source\%1
>
> call build_%1
>
> cd %embedinc%\source\%1

So you created a separate BAT file for each buildable source module in the
SOURCE directory?  There are various SRC_xxx scripts for building
individual source modules, although you have to give them the source
directory name.  For example:

  src_aspic pics hal_intr

will build the HAL_INTR.ASPIC module in the PICS source directory
regardless of the current working directory.  You can also set the
environment variable DBG_SOURCE to a testing directory, and source modules
will be taken from there if they exist.  When you're done testing, you set
DBG_PROMOTE=true, which takes the source files from the DBG_SOURCE
directory and moves them to the official source directory before using
them.


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

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu