^{Highley Recommended, Inc.}

NAVIGATION	ENVIRONMENT SET-UP
CM Home CM Resources SCM Policy Help Requests Release Procedure Compatibility Matrix Online Support Make Process Release Requests	Back to Makefile Reference Wind River Tornado Tools If you have control of your Tornado tool environment variables and you set them to what is listed below you will be able to build the Product A and Product B products without making changes to the environment variables. This has been tested on a system that only has ClearCase installed so we are confident that we have captured what is required to do a product build into the ClearCase CM system for the new build process. Right click on My Computer icon Select Properties from menu Select Environment tab Modify User Variables for UserName as defined below GCC_EXEC_PREFIX=\vendor\tornado\host\x86-win32\lib\gcc-lib\ PATH=\vendor\tornado\host\x86-win32\bin;D:\mks\mksnt SRC_BASE=\dev\producta WIND_BASE=\vendor\tornado WIND_HOST_TYPE=x86-win32 WIND_LMHOST=HOSTNAME WIND_REGISTRY=HOSTNAME The variables above were in the user environment space so the PATH variable gets appended to the system PATH variable. If you have the MKS tools installed on your system then you should move the MKS PATH settings to the user environment PATH variable after the Tornado setting. What can we say WindRiver has a broken set-up, but we are not able to fix it at this time. To change between products and do a build use the following view rules. Product B Config. Spec. element * .../release1/LATEST element * /main/LATEST Product A Config. Spec. element * V2.00.19 element * TORNADO1 element * /main/LATEST We were able to build both products in the same view by changing the view rules between builds. There is are no driver references in the paths above so a view mapped to any drive will work without changes. Different Shell Programs Windows Command Prompt(CMD.EXE) There are a few things that can be done to make the Windows command shell a little more useful. Modify the menu or desktop short cut to start you in a location and to run the doskey utility to define command aliases and macros. The menu short cut can be modified by selecting: Left click Start menu Left click Settings menu Left click Taskbar menu Select Start Menu Programs Left click Advanced button Brows Programs folder Right click on Command Prompt Select Properties Select Shortcut tab Replace Target line with: %SystemRoot%\system32\cmd.exe /k cd %USERPROFILE% & doskey /MACROFILE=%USERPROFLE%\doskey_menus.txt Select Options tab and click QuickEdit Mode and Insert Mode options. Your command window will now be in insert mode by default so you can position the cursor with the arrow keys and begin typing. You can also paste from the windows clip board by right mouse button clicking. Select Layout tab and set Screen Buffer Size Height to something like 5000 lines. This will give 5000 lines of scrolling. You might want to set the Window Size Height to 50. You can change a desktop link by righ clicking on the icon, selecting Properties and following the instructions above. One of the steps above was to run the doskey utility when you start the command prompt program and read a macro definition file. Below is an example of some of the things you might want to define in the file. If you have defined the target line as documented above then this file should be \Winnt\Profiles\UserName\doskey_menu.txt: ct=cleartool $* mt=multitool $* ls=dir /w /p $* lsf=dir /w /p $* ll=dir /p $* rm=del $* cp=copy $* cat=type $* mv=move $* vi=gvim $* swc_app=cmd.exe /k "cd \product\target\config\swc\swc_st & clearmake -C gnu" mca_app=cmd.exe /k "cd \product\target\config\mca\mca_st & clearmake -C gnu" Command Prompt has a history window which not many people know about which can be accessed by pressing the F7 key. Scroll to the line you want to re-execute and press Enter. MKS Korn Shell Below is an example file for the MKS Korn Shell program. Create the file \Winnt\Profiles\UserName\profile.ksh: #!c:/mks/mksnt/sh PS1="$COMPUTERNAME-> " alias lsf='ls -F' alias ll='ls -l' alias ct=cleartool alias less=more alias pdi_app='wstart -d /product/target/config/pdi/pdi_st sh -i' alias mca_app='wstart -d /product/target/config/mca/mca_st sh -i' EDITOR=vi; export EDITOR umask 022 Change the editor to the one of your choice. Cygwin Bash Shell Cygwin is a free port of GNU software to run native on Windows systems. Currently you can install this software from //Fargo/pub/cygwin by running the setup program. By default it will install to C:\cygwin location and create a desktop link to the bash shell command. When you are in the a bash shell the root of the file system, /, becomes C:\cygwin. Your home directory then should be /home/UserName so the file below should /home/UserName/.bashrc: #!/bin/bash PATH=/bin:/usr/bin:$PATH export PATH PS1="$COMPUTERNAME-> " TMP=/cygdrive/c/TEMP; export TMP alias lsf='ls -F' alias ll='ls -l' alias ct=cleartool alias vi=gvim alias r='fc -s' EDITOR=gvim; export EDITOR PAGER=less; export PAGER set -o vi MANPATH=$MANPATH:/usr/local/man; export MANPATH INFOPATH=$INFOPATH:/usr/local/info; export INFOPATH umask 022

NAVIGATION

ENVIRONMENT SET-UP

CM Home
CM Resources
SCM Policy
Help Requests
Release Procedure
Compatibility Matrix
Online Support
Make Process
Release Requests

Back to Makefile Reference

Wind River Tornado Tools

If you have control of your Tornado tool environment variables and you set them to what is listed below you will be able to build the Product A and Product B products without making changes to the environment variables. This has been tested on a system that only has ClearCase installed so we are confident that we have captured what is required to do a product build into the ClearCase CM system for the new build process.

Right click on My Computer icon
Select Properties from menu
Select Environment tab

Modify User Variables for UserName as defined below

GCC_EXEC_PREFIX=\vendor\tornado\host\x86-win32\lib\gcc-lib\
PATH=\vendor\tornado\host\x86-win32\bin;D:\mks\mksnt
SRC_BASE=\dev\producta
WIND_BASE=\vendor\tornado
WIND_HOST_TYPE=x86-win32
WIND_LMHOST=HOSTNAME
WIND_REGISTRY=HOSTNAME

The variables above were in the user environment space so the PATH variable gets appended to the system PATH variable. If you have the MKS tools installed on your system then you should move the MKS PATH settings to the user environment PATH variable after the Tornado setting.

What can we say WindRiver has a broken set-up, but we are not able to fix it at this time.

To change between products and do a build use the following view rules.

Product B Config. Spec.

element * .../release1/LATEST
element * /main/LATEST

Product A Config. Spec.

element * V2.00.19
element * TORNADO1
element * /main/LATEST

We were able to build both products in the same view by changing the view rules between builds. There is are no driver references in the paths above so a view mapped to any drive will work without changes.

Different Shell Programs

Windows Command Prompt(CMD.EXE)

There are a few things that can be done to make the Windows command shell a little more useful.

Modify the menu or desktop short cut to start you in a location and to run the doskey utility to define command aliases and macros. The menu short cut can be modified by selecting:

Left click Start menu
Left click Settings menu
Left click Taskbar menu
Select Start Menu Programs
Left click Advanced button
Brows Programs folder
Right click on Command Prompt
Select Properties
Select Shortcut tab

Replace Target line with:

    %SystemRoot%\system32\cmd.exe /k cd %USERPROFILE% & doskey /MACROFILE=%USERPROFLE%\doskey_menus.txt

Select Options tab and click QuickEdit Mode and Insert Mode options. Your command window will now be in insert mode by default so you can position the cursor with the arrow keys and begin typing. You can also paste from the windows clip board by right mouse button clicking.
Select Layout tab and set Screen Buffer Size Height to something like 5000 lines. This will give 5000 lines of scrolling. You might want to set the Window Size Height to 50.

You can change a desktop link by righ clicking on the icon, selecting Properties and following the instructions above.

One of the steps above was to run the doskey utility when you start the command prompt program and read a macro definition file. Below is an example of some of the things you might want to define in the file. If you have defined the target line as documented above then this file should be \Winnt\Profiles\UserName\doskey_menu.txt:

ct=cleartool $*
mt=multitool $*
ls=dir /w /p $*
lsf=dir /w /p $*
ll=dir /p $*
rm=del $*
cp=copy $*
cat=type $*
mv=move $*
vi=gvim $*
swc_app=cmd.exe /k "cd \product\target\config\swc\swc_st & clearmake -C gnu"
mca_app=cmd.exe /k "cd \product\target\config\mca\mca_st & clearmake -C gnu"

Command Prompt has a history window which not many people know about which can be accessed by pressing the F7 key. Scroll to the line you want to re-execute and press Enter.

MKS Korn Shell

Below is an example file for the MKS Korn Shell program. Create the file \Winnt\Profiles\UserName\profile.ksh:

#!c:/mks/mksnt/sh
PS1="$COMPUTERNAME-> "
alias lsf='ls -F'
alias ll='ls -l'
alias ct=cleartool
alias less=more
alias pdi_app='wstart -d /product/target/config/pdi/pdi_st sh -i'
alias mca_app='wstart -d /product/target/config/mca/mca_st sh -i'
EDITOR=vi; export EDITOR
umask 022

Change the editor to the one of your choice.

Cygwin Bash Shell

Cygwin is a free port of GNU software to run native on Windows systems. Currently you can install this software from //Fargo/pub/cygwin by running the setup program. By default it will install to C:\cygwin location and create a desktop link to the bash shell command. When you are in the a bash shell the root of the file system, /, becomes C:\cygwin. Your home directory then should be /home/UserName so the file below should /home/UserName/.bashrc:

#!/bin/bash

PATH=/bin:/usr/bin:$PATH
export PATH

PS1="$COMPUTERNAME-> "

TMP=/cygdrive/c/TEMP; export TMP

alias lsf='ls -F'
alias ll='ls -l'
alias ct=cleartool
alias vi=gvim
alias r='fc -s'
EDITOR=gvim; export EDITOR
PAGER=less; export PAGER
set -o vi
MANPATH=$MANPATH:/usr/local/man; export MANPATH
INFOPATH=$INFOPATH:/usr/local/info; export INFOPATH
umask 022