1 Setting your Environment
2 Setting your Environment
4 In order to use the pmcc command (or any of the other commands in the
5 tools directory), you must set your environment correctly. How you do
6 this depends on the type of host you are using. Please refer to the
7 appropriate section below:
11 To set your environment, move to the directory where you unpacked the
12 PMON5 source archive and type,
16 (this assumes that you have already run the "Install" program).
18 The batch file SETENV.BAT creates a number of new environment variables
19 which often exceeds the available environment size. If this happens,
20 the operating system will usually respond with a message something like
21 "Out of Environment space". To fix this problem, add the following line
22 to your \CONFIG.SYS file:
24 SHELL=C:\DOS\COMMAND.COM C:\DOS\ /E:1024 /p
26 Where C:\DOS is the directory that contains COMMAND.COM and
27 other MSDOS utilities. This expands your environment space
30 This is also the stage where you might discover that your path
31 variable is too long. Unfortunately the only indication is
32 usually that the operating system echoes the new path to the
33 screen. So if you see a list of directories printed to the
34 screen after you type SETENV, it likely means that you need to
35 shorten your path. Unfortunately the only way to do this is
36 shorten your directory names, and move things closer to the
39 To set the environment back the way it was before, type,
43 This is especially useful if you have built more than one copy of PMON5,
44 each with different target parameters. You can then use the UNSETENV
45 command when moving from one package to another, since it is usually
46 very important to use the correct package when building a program.
50 To set your environment, move to the directory where you unpacked the
51 PMON5 source archive and type,
53 source.csh -- csh or tcsh
56 csh and tcsh users should note that they might need to type 'rehash'
57 before the pmcc command is recognized.
59 Note also that this only sets the environment in the current shell. If
60 you decide to use a different window you will need to repeat this
61 procedure. On the other hand, if you have built more than one copy of
62 PMON5, each with different target parameters, you must use a different
63 window for each package, and be certain to set the enviroment of each
64 window correctly before compiling any programs.
66 Note that you should not set the environment unnecessarily as it will
67 keep expanding your environment size and possibly cause you to run
68 out of space. The general rule is; If you get the message "Command
69 not found." (or something like that) after issuing the pmcc command,
70 you likely need to set your environment.
72 ««««««««««««««««««««««««««««««««««««««««»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»
79 **This file was converted from HTML to TEXT using a TRIAL version of**
80 **Markup Remover 1.1 (C) 1998 by Aquatic Moon Software http://www.aquaticmoon.com/**
81 **This message does not appear in files converted after the program has been liscensed.**