Alan B. Pearce wrote:
> C:\embedinc\source\ADMRC>make_pic_project
> Missing project name parameter.

It is not intended that you be in the SOURCE directory during development,
and the MAKE_PIC_PROJECT script is certainly not intended to be run there.
It might make quite a mess.  It is intended to be run in your own user
directory in a subdirectory with the same name as the SOURCE and SRC
directories you are working with.  It must also be run only after the
environment is set up by the SOURCE_DIR script.  Assuming your home
directory is c:\alan, the transcript should look something like this:

  c:\someplace>source_dir admrc

  Directory c:\alan\admrc

  C:\alan\admrc>make_pic_project ctl 16f628a

This will create the ADMRC subdirectories in EMBED\SOURCE and EMBED\SRC and
will create a bunch of template project files in ALAN\ADMRC.

> 'upcase_arg' is not recognized as an internal or external command,
> operable program or batch file.
> 'downcase_arg' is not recognized as an internal or external command,
> operable program or batch file.
> 'slink' is not recognized as an internal or external command,
> operable program or batch file.
> File not found.  File name was "(cog)source/pic/build_qqq_expic.bat"
> with suffix string "".
> Error on trying to open input file
> "(cog)source/pic/build_qqq_expic.bat" for text read.
> *** Program aborted on error. ***
> 'slink' is not recognized as an internal or external command,
> operable program or batch file.

These files were missing in the release.  This has been fixed.
http://www.embedinc.com/pic/dload.htm

> It would seem prudent to have all these missing files in the picdev
> package, so people not wishing to have the public source installed can
> make a complete development installation without needing to install the
> public source package as well.

Of course, but I don't always think of updating the release scripts when
making changes to the environment while trying to get a project done.  There
is no easy way to test this on my end since my machines all have the files.
Setting up one or my machines for a virgin install is more disruptive and
more work than you probably imagine.

> The other problem I have is if an attempt is made to create a project
> in a directory that is a subdirectory of a directory name that has
> spaces in it (e.g. "C:\Documents and Settings\") as the batch files
> cannot handle the spaces, and separate the words, attempting to use
> them as commands.

Yeah, I know there are still places lurking in the scripts where that is a
problem.  Personally, I think directories names and file names with spaces
is a really bad idea, but I've been slowly updating the scripts to make them
tolerant of spaces when I'm in there making changes anyway.  Dealing with
spaces in pathnames is something that must be carefully done and thought
about on nearly every line of a CMD script.  I've been trying to write newer
scripts to work that way, but there are still a bunch of older scripts that
haven't been updated in a while.  For now the answer is "Don't do that".

> I haven't attempted to modify them
> to include the directories in quotes or anything like that,

It's not nearly that simple.


********************************************************************
Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
(978) 742-9014.  Gold level PIC consultants since 2000.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist