James Newton, Host wrote:
> Anyway, just a thought. Multiple files specific to each project kills
> it.

It is possible to do a project in a single project-unique file, but much of
the power of the development environment and modularization is lost if you
do that.  I tend to use single files only for my 10F and a few 12F projects.
I suppose it would be possible to create a template where you set a few
configuration constants at the top, it takes care of a bunch of mechanics
largely using canned include files, then has a banner labeled INSERT YOUR
CODE HERE.  That might actually be instructive to get into PICs easily but
starting with the right discipline.  There would still need to be a way to
communicate the target PIC type outside the file so that the build procedure
can select the proper linker file.  There will have to be a custom wrapper
program that parses the PIC type from the source file, runs all the tools in
the right sequence, reports and aborts on errors, and hands back your .COD
and .HEX files on success.

So I guess it's possible to do within some restrictions and it wouldn't be
hard to create the single build tool, but would anyone actually use it?

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist