Searching \ for '[PIC]: Olin Lathrop's development environment' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/languages.htm?key=environ
Search entire site for: 'Olin Lathrop's development environment'.

Exact match. Not showing close matches.
PICList Thread
'[PIC]: Olin Lathrop's development environment'
2003\02\07@172259 by Dwayne Reid

flavicon
face
At 04:28 PM 2/7/03 -0500, Olin Lathrop wrote:

>Click on the SOFTWARE DOWNLOADS link at the bottom of the page to download
>the complete PIC build environment that these macros are a part of.

Olin - I'd love to look at your code processing utilities.  However, I run
Win 98SE and your installation routines don't work with that OS.

Does the installation routine make changes to the operating environment
(registry entries, environment variables, path, etc) or does it just create
the directory structure and install the files.  If it is the latter, would
it possible to get a ZIP version instead?  ZIP files can be told to
preserve the directory structure and would allow those of us who are stuck
with an older OS to still make use of your system.

Many thanks!

dwayne

--
Dwayne Reid   <spam_OUTdwaynerTakeThisOuTspamplanet.eon.net>
Trinity Electronics Systems Ltd    Edmonton, AB, CANADA
(780) 489-3199 voice          (780) 487-6397 fax

Celebrating 18 years of Engineering Innovation (1984 - 2002)
 .-.   .-.   .-.   .-.   .-.   .-.   .-.   .-.   .-.   .-
    `-'   `-'   `-'   `-'   `-'   `-'   `-'   `-'   `-'
Do NOT send unsolicited commercial email to this email address.
This message neither grants consent to receive unsolicited
commercial email nor is intended to solicit commercial email.

--
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

2003\02\07@180429 by Olin Lathrop

face picon face
> Olin - I'd love to look at your code processing utilities.  However, I
run
> Win 98SE and your installation routines don't work with that OS.

Right.  I never had a good reason (a paying customer) to support software
installation on Win9x.

> Does the installation routine make changes to the operating environment
> (registry entries, environment variables, path, etc) or does it just
create
> the directory structure and install the files.  If it is the latter,
would
> it possible to get a ZIP version instead?  ZIP files can be told to
> preserve the directory structure and would allow those of us who are
stuck
> with an older OS to still make use of your system.

The installation procedure does more than just copy a directory.  It
creates/modifies environment variables and runs shell command, both of
which differ between Win9x and NT.  If you run it on Win9x it could make a
mess.

The software can be installed on Win9x.  It's a manual procedure and isn't
for dummies.  I don't publisize it because I don't want to hear the
complaints from people that mess it up.  It's actually very easy to do,
but I've had otherwise intelligent people simply not follow the
directions, then get mad at me when it doesn't work.  It's just easier to
say the software isn't for Win9x.

If you promise not to complain about the procedure (I might be willing to
help with problems, but not if you complain), I'll tell you how to do it.
Psst, don't tell everyone else or some bozo will try it without actually
reading the directions <g>.

Run the INSTALL_PICDEV.EXE file.  This will run the Winzip self extractor
and then bring up a command shell window.  DO NOT TYPE ANYTHING IN THE
COMMAND SHELL WINDOW.  The purpose of running INSTALL_PICDEV.EXE is just
to get the zipped directory expanded somewhere on your disk.  At the top
of the window it will show the installation source directory.  That is
where the zip file got expanded to.  Leave the command shell window open
and go one level above the indicated directory using another window.  For
example, if the message says:

 Software installation source directory is C:\temp\WZSE0.TMP\embedinc.

then go to C:\temp\WZSE0.TMP.  That directory is a regular Embed Inc
software release directory.  Look at the README.TXT file and follow the
directions for Win9x installation.  Note that you do not run INSTALL.EXE
for Win9x.  This should be obvious from the directions, but nonetheless
people have done that then blamed me for a messed up installation.  Once
you are done with the installation directory and before you reboot the
system, make sure you are no longer in the installation directory, then
close the window that came up when you ran INSTALL_PICDEV.EXE.  That will
delete the temporary installation directory from your system, which you
don't need anymore.  Now reboot as the directions say.


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

--
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

2003\02\08@011005 by Dwayne Reid

flavicon
face
At 06:03 PM 2/7/03 -0500, Olin Lathrop wrote:
> > Olin - I'd love to look at your code processing utilities.  However, I
>run
> > Win 98SE and your installation routines don't work with that OS.
>
>Right.  I never had a good reason (a paying customer) to support software
>installation on Win9x.
>
>The software can be installed on Win9x.  It's a manual procedure and isn't
>for dummies.  I don't publisize it because I don't want to hear the
>complaints from people that mess it up.  It's actually very easy to do,
>but I've had otherwise intelligent people simply not follow the
>directions, then get mad at me when it doesn't work.

Olin - your directions for installing PICDEV were extremely clear and very
easy to follow.  Thanks for making it so easy!  Guess what I get to play
with this weekend!

I also installed the project files as well: HAL, HOS, Chess and Wave but
I'm not sure that my assumptions were valid.  The install packages had the
same directory structure as the main dev package so I assumed that they all
installed in the same directories.  In the case of duplicate file names, I
kept the files with the most recent date.  It looks as if only one of those
has changed: the PICDEV package contained a larger version of
"file.msg".  Since it was also the most recent file date, I just kept it.

However, I'm not convinced that I made the right choice.  Should I have
created separate child sub-directories off of SOURCE for each project?  In
other words, should I have created a directory called
'c:\embedinc\source\hal' for the HAL source files?  Right now, all the
source code files are in a directory called 'c:\embedinc\source\pics'.

Thanks again!

dwayne

--
Dwayne Reid   <.....dwaynerKILLspamspam@spam@planet.eon.net>
Trinity Electronics Systems Ltd    Edmonton, AB, CANADA
(780) 489-3199 voice          (780) 487-6397 fax

Celebrating 18 years of Engineering Innovation (1984 - 2002)
 .-.   .-.   .-.   .-.   .-.   .-.   .-.   .-.   .-.   .-
    `-'   `-'   `-'   `-'   `-'   `-'   `-'   `-'   `-'
Do NOT send unsolicited commercial email to this email address.
This message neither grants consent to receive unsolicited
commercial email nor is intended to solicit commercial email.

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.

2003\02\08@082401 by Olin Lathrop

face picon face
> Olin - your directions for installing PICDEV were extremely clear and very
> easy to follow.  Thanks for making it so easy!  Guess what I get to play
> with this weekend!

Thanks, it's really not hard as long as you are willing to *read* the
directions.  Unfortunately too many people don't.

Let me know how you make out with the stuff.

> I also installed the project files as well: HAL, HOS, Chess and Wave but
> I'm not sure that my assumptions were valid.  The install packages had the
> same directory structure as the main dev package so I assumed that they
all
> installed in the same directories.  In the case of duplicate file names, I
> kept the files with the most recent date.  It looks as if only one of
those
> has changed: the PICDEV package contained a larger version of
> "file.msg".  Since it was also the most recent file date, I just kept it.

That was the right thing to do.  Click on the "CLICK HERE for directions on
how to install a software release" link at the top of the page you
downloaded the software from.  It explains how to install multiple releases
and demystifies the directory structure.  Multiple releases must be
installed in oldest to newest order.  Note that dates are given for all
software releases, partly for that purpose.

> However, I'm not convinced that I made the right choice.  Should I have
> created separate child sub-directories off of SOURCE for each project?  In
> other words, should I have created a directory called
> 'c:\embedinc\source\hal' for the HAL source files?  Right now, all the
> source code files are in a directory called 'c:\embedinc\source\pics'.

Embed Inc software all lives in one tree.  Each release contains whatever
subset of that tree it needs.  You can name the whole embedinc directory
whatever you want and place it wherever you want, but don't rename or move
around anything inside that tree.  A bunch of generic projects live in the
PICS source directory, including the HAL and HOS projects.  The PICS
directory is sortof my generic PIC play area.  It contains stuff I'm usually
willing to give out.  Real projects live in other diretories that aren't on
any of the releases or course.

The BUILD_HAL_EXPIC and BUILD_HOS_EXPIC scripts, for example, assume that
these projects are in the PICS directory.  Again, see
http://www.embedinc.com/swdload.htm.


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

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.

2003\02\10@061405 by Alan B. Pearce

face picon face
Dwayne Reid wrote

>Olin - your directions for installing PICDEV were extremely
>clear and very easy to follow.  Thanks for making it so easy!
>Guess what I get to play with this weekend!

You will have fun with these Dwayne.

I built myself a little batch file to make using Olin's system slightly
easier in the use I was putting them to, as mine is a multi-PIC project. I
created separate project directories for each project, with all the files
required for each, in them, and then used this batch file to build each
portion of the project as necessary. Put this file in a directory which is
included in the path statement (in my case C:\embedinc\com), and when the
build process is finished, it leaves the DOS window in the source project
directory of the project just built.

So if you had the HAL project in C:\embedinc\hal, then the command to type
would be "build hal", instead of going to the HAL directory to type
"build_hal". In my case having this file up front saved having to do lots of
directory changes when building more than one PIC in the project, in rapid
succession. :)) You will see that there is a CLS instruction which has been
"rem'd" out, that can be included if desired.

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.

=== File "Build.Bat" ===

@echo off
rem
rem   BUILD <.INS.ASPIC file name>
rem

rem cls
cd %embedinc%\source\%1

call build_%1

cd %embedinc%\source\%1

=== End Of File ===

--
http://www.piclist.com hint: To leave the PICList
piclist-unsubscribe-requestspamKILLspammitvma.mit.edu>

2003\02\10@083923 by Olin Lathrop

face picon face
> 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.

{Quote hidden}

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
.....piclist-unsubscribe-requestKILLspamspam.....mitvma.mit.edu>

2003\02\10@121654 by Alan B. Pearce

face picon face
>So you created a separate BAT file for each buildable
>source module in the SOURCE directory?

Correct. That seemed to be the way you had done it on the environment I
originally received from you, and each build file then has only the
appropriate source names for that project. I also did another modification
to the individual build files so that the linker file gets the file names
automatically entered into it.

=== build_hkp.bat ===

@echo off
rem
rem   BUILD_HKP
rem
rem   Build the HKP PIC project.
rem

call src_ins_aspic hkp hkplib
call src_ins_aspic hkp hkp

rem delete existing file to allow a rebuild of it.
del hkp.mlist

call src_aspic hkp hkp_a2d
call src_aspic hkp hkp_d2a
call src_aspic hkp hkp_i2c
call src_aspic hkp hkp_init
call src_aspic hkp hkp_intr
call src_aspic hkp hkp_main
call src_aspic hkp hkp_port
call src_aspic hkp hkp_prom
call src_aspic hkp hkp_reg
call src_aspic hkp hkp_rly
call src_aspic hkp hkp_strt
call src_aspic hkp hkp_slav
call src_aspic hkp hkp_uart

copya -out hkp.libpic -s "/c"
copya -out hkp.libpic -append -s hkp.lib
copya -out hkp.libpic -append -in hkp.mlist
libpic hkp.libpic

copya (cog)source/pic/p16f876i.linkpic hkp.lkr
copya -out hkp.lkr -append -s "LIBPATH ."
copya -out hkp.lkr -append -s "FILES hkp_strt.o"
copya -out hkp.lkr -append -s "FILES hkp.lib"
linkpic hkp

=== end of file ===

note the line "del hkp.mlist". I then modified src_aspic.bat to build this
file like so, so that it rebuilds hkp.mlist with the names of the files that
need to be linked, without having to maintain multiple files when another
module was added to the project.

=== src_aspic.bat ===

@echo off
rem
rem   SRC_ASPIC <src dir lnam> <.ASMPIC file name>
rem
rem   Build a PIC assembler source file.  The first argument is the
rem   leafname of the source directory.  The second is the generic name
rem   of the source file.  The file will be copied into the approriate
rem   SRC directory and assembled.
rem

call src_get %1 %2.aspic
asmpic %2.aspic /c- /o+ /t4
copya -out %1.mlist -append  -s %2.o

=== end of file ===

However it sounds like you have modified the batch files quite a bit since I
originally obtained these from your site, so my modifications may not map
straight into your current methodology. I will have to look at the new files
to see.

--
http://www.piclist.com hint: To leave the PICList
EraseMEpiclist-unsubscribe-requestspam_OUTspamTakeThisOuTmitvma.mit.edu>

2003\02\10@134311 by Olin Lathrop

face picon face
> >So you created a separate BAT file for each buildable
> >source module in the SOURCE directory?
>
> Correct. That seemed to be the way you had done it on the environment I
> originally received from you, and each build file then has only the
> appropriate source names for that project.

Actually you did it per resulting executable, not per module.  The
comments in your last post implied it was per module, but that was
probably because they weren't updated after a cut and paste.

> I also did another modification
> to the individual build files so that the linker file gets the file
names
{Quote hidden}

This looks like it was modified from a rather old version.  This may have
been before the SRC_LIBPIC and SRC_EXPIC scripts existed.  The new version
of BUILD_HAL_EXPIC.BAT looks like this:

 ...
 call src_aspic pics hal_s22
 call src_aspic pics hal_s35

 call src_aspic pics hal_strt

 call src_libpic pics hal
 call src_expic pics hal

> note the line "del hkp.mlist". I then modified src_aspic.bat to build
this
> file like so, so that it rebuilds hkp.mlist with the names of the files
that
> need to be linked, without having to maintain multiple files when
another
> module was added to the project.

Very nice.  I've been meaning to do something like that.  I would do the
delete like this:

 if exist hkp.mlist del hkp.mlist

because otherwise it would not run the first time or after the SRC
directory got cleaned out.  I was also thinking of checking for the
existance of the MLIST file in the SOURCE directory and appending its
contents to the automatically created list.  This leaves a way to
explicitly specify additional modules to add to the library, although I've
never needed to do that so far.  The only other problem I would have with
your method is that the automatic MLIST file is named from the source
directory, not the resulting buildable.  I guess it wouldn't be a problem
unless you were doing concurrent builds.

> However it sounds like you have modified the batch files quite
> a bit since I originally obtained these from your site, so my
> modifications may not map straight into your current methodology.
> I will have to look at the new files to see.

Yes, things have changed a little.  I really don't like the BAT file
method at all, although it's kind of "good enough" now.  The BAT files are
a stopgap between the old source code control and build system dying
because it only ran on ancient museum piece computers, and the new system
I am working on.  The heart of the new system is an intelligent command
line interpreter that is vastly superior to CMD.


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

--
http://www.piclist.com hint: To leave the PICList
piclist-unsubscribe-requestspamspam_OUTmitvma.mit.edu>

2003\02\10@135732 by Dwayne Reid

flavicon
face
At 01:42 PM 2/10/03 -0500, Olin Lathrop wrote:

>The heart of the new system is an intelligent command
>line interpreter that is vastly superior to CMD.

Is this something that already exists or something that you are writing?  I
spend most of my life at the command line - anything that makes it easier
is something I'd like to learn about, if possible.

Thanks!

dwayne


--
Dwayne Reid   <@spam@dwaynerKILLspamspamplanet.eon.net>
Trinity Electronics Systems Ltd    Edmonton, AB, CANADA
(780) 489-3199 voice          (780) 487-6397 fax

Celebrating 18 years of Engineering Innovation (1984 - 2002)
 .-.   .-.   .-.   .-.   .-.   .-.   .-.   .-.   .-.   .-
    `-'   `-'   `-'   `-'   `-'   `-'   `-'   `-'   `-'
Do NOT send unsolicited commercial email to this email address.
This message neither grants consent to receive unsolicited
commercial email nor is intended to solicit commercial email.

--
http://www.piclist.com hint: To leave the PICList
KILLspampiclist-unsubscribe-requestKILLspamspammitvma.mit.edu>

2003\02\10@143055 by Olin Lathrop
face picon face
> >The heart of the new system is an intelligent command
> >line interpreter that is vastly superior to CMD.
>
> Is this something that already exists or something that you are writing?
I
> spend most of my life at the command line - anything that makes it
easier
> is something I'd like to learn about, if possible.

It is something that I am creating and is partially working.  Frankly, CMD
sucks.  There are shells available that originated on old unix systems,
but use cryptic syntax and of course aren't built on my file system
abstraction layer.  This layer gives me consistant path naming and other
features accross platforms and some interoperability between platforms.
For example, it always provides symbolic links whether the underlying
system has them or not (see the SLINK command).  I plan on adding source
code directory structure awareness to the file system layer, then using
that to write intelligent build scripts using the shell.  Now if other
things didn't keep getting in the way...


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

--
http://www.piclist.com hint: To leave the PICList
RemoveMEpiclist-unsubscribe-requestTakeThisOuTspammitvma.mit.edu>

2003\02\10@161031 by William Chops Westfield

face picon face
Are you familiar with CCMD?  I'm not sure it's very related to what you're
trying to do, but this is a tool that was developed for helping tops20 users
and programmers migrate to unix systems.  It's a C library that implements
most of the tops20 command parser, including command and filename completion,
guid words, context sensitive help, and s on.  IMO, tops20 provided the
epitomy of command line interfaces, and CCMD provides most of the features
for unix/dos/etc.  I've always wanted a CCMD based cli for modern computer
hardware...

BillW

--
http://www.piclist.com hint: To leave the PICList
spamBeGonepiclist-unsubscribe-requestspamBeGonespammitvma.mit.edu>

2003\02\10@162317 by

flavicon
face
Or "DCL Light", if you'd like something like OpenVMS DCL
command line interface. Havn't tried it, I'm currently
downloaoding...
http://www.accelr8.com/dcll.html

Jan-Erik Söderholm
(a VMS fan)

William Chops Westfield wrote :
> Are you familiar with CCMD? It's a C library that implements
> most of the tops20 command parser, including command and filename
> completion, guid words, context sensitive help, and s on.

--
http://www.piclist.com hint: To leave the PICList
TakeThisOuTpiclist-unsubscribe-requestEraseMEspamspam_OUTmitvma.mit.edu>


'[PIC]: Olin Lathrop's development environment'
2003\04\07@150523 by Russ Hensel
picon face
source= http://www.piclist.com/postbot.asp?id=piclist\2003\02\07\172259a


I have been messing around with the environment and discoverd that you can just change the extension on the file from exe to
zip.

there is a c: hardcoded in at least one of the batch files
therefore put the code somewhere on your c: drive or search for the c: and change to the appropriate drive.

Olin tells me ( see http://www.piclist.com/techref/postbot.asp?by=time&id=piclist\2003\04\03\170251a&tgt=post ) that the files not under embedinc can be discarded.




---
Russ  Hensel
http://www.piclist.com/member/RH-yahoo-P43
PIC/PICList FAQ: http://www.piclist.com

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

2003\04\07@161113 by Olin Lathrop

face picon face
> there is a c: hardcoded in at least one of the batch files
> therefore put the code somewhere on your c: drive or search for the c:
> and change to the appropriate drive.

I just did a scan, and found the c: in SRC_GET.BAT.  Argh, if CMD would
only let you pass the output of one command as a parameter to another.
Or, if the CD command allowed you to pass a complete pathname instead of a
path only on the current drive.  The C: is there to set the drive where
the EMBEDINC directory is assumed to be.  I guess the installation program
should create additional variables like EMBEDINC_DRIVE and EMBEDINC_PATH
for this purpose.  Someday.


*****************************************************************
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

2003\04\07@170438 by Ned Konz

flavicon
face
On Monday 07 April 2003 01:09 pm, Olin Lathrop wrote:
> > there is a c: hardcoded in at least one of the batch files
> > therefore put the code somewhere on your c: drive or search for
> > the c: and change to the appropriate drive.
>
> I just did a scan, and found the c: in SRC_GET.BAT.  Argh, if CMD
> would only let you pass the output of one command as a parameter to
> another.

You can:

for /f "usebackq" %%i in (`some command`) do some other command %i

> Or, if the CD command allowed you to pass a complete
> pathname instead of a path only on the current drive.

You can:

cd /c d:\xyz

Of course, both require a proper cmd.exe (command.com need not apply).

But then MS-DOS and the Win3 derivatives (Win9x) are increasingly
irrelevant anyway.

--
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE

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

2003\04\07@171727 by Ned Konz

flavicon
face
On Monday 07 April 2003 02:02 pm, Ned Konz wrote:
> On Monday 07 April 2003 01:09 pm, Olin Lathrop wrote:
> > > there is a c: hardcoded in at least one of the batch files
> > > therefore put the code somewhere on your c: drive or search for
> > > the c: and change to the appropriate drive.
> >
> > I just did a scan, and found the c: in SRC_GET.BAT.  Argh, if CMD
> > would only let you pass the output of one command as a parameter
> > to another.
>
> You can:
>
> for /f "usebackq" %%i in (`some command`) do some other command %i

er...

inside a batch file:
for /f "usebackq" %%i in (`some command`) do some other command %%i

on the command line:
for /f "usebackq" %i in (`some command`) do some other command %i

--
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE

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

2003\04\08@052414 by hael Rigby-Jones

picon face
> -----Original Message-----
> From: Ned Konz [SMTP:RemoveMEnedspamTakeThisOuTBIKE-NOMAD.COM]
> Sent: Monday, April 07, 2003 10:02 PM
> To:   PICLISTEraseMEspam.....MITVMA.MIT.EDU
> Subject:      Re: [PIC]: Olin Lathrop's development environment
>
> You can:
>
> cd /c d:\xyz
>
> Of course, both require a proper cmd.exe (command.com need not apply).
>
On Windows NT at least, this should be cd /d d:\xyz

Regards

Mike


=======================================================================
This e-mail is intended for the person it is addressed to only. The
information contained in it may be confidential and/or protected by
law. If you are not the intended recipient of this message, you must
not make any use of this information, or copy or show it to any
person. Please contact us immediately to tell us that you have
received this e-mail, and return the original to us. Any use,
forwarding, printing or copying of this message is strictly prohibited.
No part of this message can be considered a request for goods or
services.
=======================================================================
Any questions about Bookham's E-Mail service should be directed to EraseMEpostmasterspambookham.com.

--
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

2003\04\08@081554 by Olin Lathrop

face picon face
> for /f "usebackq" %%i in (`some command`) do some other command %i
>
> cd /c d:\xyz

Thanks, I didn't know about this.


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

--
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

2003\04\08@100804 by Ned Konz

flavicon
face
On Tuesday 08 April 2003 02:21 am, Michael Rigby-Jones wrote:
> > -----Original Message-----
> > From: Ned Konz [SMTP:RemoveMEnedEraseMEspamEraseMEBIKE-NOMAD.COM]
> > Sent: Monday, April 07, 2003 10:02 PM
> > To:   RemoveMEPICLISTspam_OUTspamKILLspamMITVMA.MIT.EDU
> > Subject:      Re: [PIC]: Olin Lathrop's development environment
> >
> > You can:
> >
> > cd /c d:\xyz
> >
> > Of course, both require a proper cmd.exe (command.com need not
> > apply).
>
> On Windows NT at least, this should be cd /d d:\xyz

Yes. Sorry about the typo.

--
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE

--
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

2003\04\08@212302 by Russ Hensel

picon face
source= http://www.piclist.com/postbot.asp?id=piclist\2003\02\10\083923a

I am not sure that this is completely relevant, but it seems to me what you
are looking for is not an interactive environment but rather a scripting
language or build tool.  In the Java community a build tool called Ant is
very popular.  It has a bunch of nice features:

Open source, free
Runs on pretty much any platform
Setup if more descriptive than procedural.
Very good at moving files, deleting files, and building lists of files and
feeding them to other tasks.
Extensible by running progmas in the environment of the host machine.
Also extensible by writing programs specifically for it ( most commonly in
java ).
Once a build is specified ( in an xml file ) either parts of the build or
the whole thing can be run from the command line.
Includes options for output often very useful for debugging.
Documented and actively maintaind.

Not so nice features.

Needs a java environment, I think just runtime, I have usually used the
whole sdk.  Free, but a lot of stuff to put on your computer if you have no
interest in Java.

Powerful but with that comes some complexity.

Overall might be worth a look:

http://ant.apache.org/

If you want to roll your own from a scripting language there are a ton:

Perl, Python, ....

Some of these have quite a learing curve themselves.  I think TCL may be a
little simpler than some of the others, but overall I would go the Ant route
( but then I do a fair amount of work in Java )  If Olin is interested I
would be willing to try to work with him to get something going.

Russ


---
Russ  Hensel
http://www.piclist.com/member/RH-yahoo-P43
PIC/PICList FAQ: http://www.piclist.com

--
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

2003\04\09@080310 by Olin Lathrop

face picon face
> I am not sure that this is completely relevant, but it seems to me what
> you are looking for is not an interactive environment but rather a
> scripting language or build tool.

You are right.  We are working on something like that now, but it's not
ready for general release.  It will be something that we can freely give
to customers who want to build our code themselves, without being a major
intrusion on their machine (like all the Java stuff you mentioned).  It
will also be layered on our OS portability interface and can therefore
make use of our special file name handling.

Our stuff used to all be built from the Apollo DSEE environment.  The BAT
files on NT are just an interim stopgap.


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

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.

2003\04\09@085356 by Dave Tweed

face
flavicon
face
Olin Lathrop <RemoveMEolin_piclistTakeThisOuTspamspamEMBEDINC.COM> wrote:
> > I am not sure that this is completely relevant, but it seems to me what
> > you are looking for is not an interactive environment but rather a
> > scripting language or build tool.
>
> You are right.  We are working on something like that now, but it's not
> ready for general release.  It will be something that we can freely give
> to customers who want to build our code themselves, without being a major
> intrusion on their machine (like all the Java stuff you mentioned).  It
> will also be layered on our OS portability interface and can therefore
> make use of our special file name handling.
>
> Our stuff used to all be built from the Apollo DSEE environment.  The BAT
> files on NT are just an interim stopgap.

In the meantime, just use Gnu make, available everywhere for all platforms
and just a single executable file. For example, the following Makefile
builds Olin's hal project. Although it ignores the "special file name
handling" (by not using Olin's asm/lib/link wrappers), doesn't put the
derived files in a separate directory and does not go to the trouble of
creating a library for each project, it could easily be extended to do all
of these things.

-- Dave Tweed

==========================================================================
# Embed/src/hal/Makefile

# Embed, Inc. tools

PREPIC = ../../com/prepic

# Microchip tools

ASM = "c:/Program Files/MPLAB/MPASMWIN"
LINK = "c:/Program Files/MPLAB/MPLINK" /k "../pic"

# Other tools

RM = del

HAL_OBJS = hal_strt.o hal_ad.o hal_eyes.o hal_init.o hal_intr.o hal_main.o \
hal_port.o hal_rand.o hal_soun.o hal_s09.o hal_s16.o hal_s22.o hal_s35.o \
owl.o howl.o pop.o pop2.o

# Embed's preprocessor

%.asm: %.aspic
       $(PREPIC) $< $@

%.inc: %.ins.aspic
       $(PREPIC) $< $@

# Assemble

%.o: %.asm
       $(ASM) /c- /q /o $@ $<

# Link

hal.hex: $(HAL_OBJS)
       echo "FILES $(HAL_OBJS)" >temp.lkr
       $(LINK) p16f876m.lkr temp.lkr /m hal.map /o $@

# Cleanup

clean:
       $(RM) *.ERR
       $(RM) *.LST
       $(RM) temp.lkr

realclean: clean
       $(RM) *.asm
       $(RM) *.inc
       $(RM) *.O
       $(RM) *.map
       $(RM) *.cod
       $(RM) *.hex

# Additional source dependencies

hal_ad.o: hal.inc hallib.inc

hal_eyes.o: hal.inc hallib.inc

hal_init.o: hal.inc hallib.inc

hal_intr.o: hal.inc hallib.inc

hal_main.o: hal.inc hallib.inc

hal_port.o: hal.inc hallib.inc

hal_rand.o: hal.inc hallib.inc

hal_s09.o: hallib.inc

hal_s16.o: hallib.inc

hal_s22.o: hallib.inc

hal_s35.o: hallib.inc

hal_soun.o: hal.inc hallib.inc

hal_strt.o: hal.inc hallib.inc

howl.o: hal.inc hallib.inc

owl.o: hal.inc hallib.inc

pop.o: hal.inc hallib.inc

pop2.o: hal.inc hallib.inc
==========================================================================

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.

More... (looser matching)
- Last day of these posts
- In 2003 , 2004 only
- Today
- New search...