build
[email protected]
BUILD
Tips on how to obtain the sourcecode and build from the VAX:
1) Receive New Non-Partition Build Mail
The integration group sends out mail which identifies the directory
used for the new non-partition build. In the most recent case for
MD90, the new directory was m902005_np. This is an engineering build,
created using local libraries, as opposed to a "swit" build which is
built directly out of ACM. An example swit directory might be
m90swit155.
2) Log onto the VAX
3) Run "integ_login" to define new logicals
$ integ_login MD90 -- defines MD90 logicals
4) Change to MD90 NP directory
$ set def m902005_np
This directory should contain 1 .abs and 1 .pth.
5) Download .abs and .pth to bangalore4
Bangalore4 is subject to space limitations. I usually try to remove
builds which are no longer used.
$ ftp 204.220.167.32
login:
password:
ftp> cd /india2/projects/du/Displays_Test/SUT
ftp> bin
ftp> put md90_np_driver.abs m902005.abs -- rename appropriately
ftp> ascii
ftp> put md90_np_driver.pth m902005.pth
ftp> exit
Execute the new build on a Bangalore DWS. For the MD90 builds,
you can execute tests from /sun/CDS/birks to see if the new
MD90 build works well. The tests which are available are
md90_pfd_check.ssi and md90_nd_check.ssi. These .ssi files
are not perfect, but they will help to answer whether the
DWS can talk to the new build.
6) Create a command procedure to fetch source code from ACM
On the VAX:
$ copy m902005_np:acm_config_contents.txt []
$ @ebwr3:[birks.hiso_tools]createfetch
This creates a file called fetch.acm. The fetch.acm file
contains ACM commands to fetch all of the appropriate
sourcefiles for the given build.
7) Log onto V node to fetch source code
This fetches hundreds of files into the current directory.
It would be wise to create a separate directory to do the
above command.
Log onto V node
$ md90srcacm
ACM> @fetch.acm
8) Copy the hundreds of .ada files to the sun
Since the sun has tools for creating a single archive file and
compressing that file, I use the sun. Similar tools may exist on
the VAX, in which case you can do this from the VAX if you choose.
$ ftp cds06
login:
password:
ftp> mput *.*
fpt> exit
9) Archive and compress all the .ada sourcefiles
Logon to sun
cds06% tar cvf m902005.tar *.ada
cds06% compress m902005.tar
This creates a compressed m902005.tar.Z file.
10) Download sourecode to bangalore5
I have previously created the directory
/india2/projects/du/Displays_Test/sourcefiles/MD90/m902005
cds06% ftp 204.220.167.31
login:
password:
ftp> cd /india2/projects/du/Displays_Test/sourcefiles/MD90/m902005
ftp> bin
ftp> mput m902005.tar.Z
ftp> exit
11) Uncompress and unextract sourcefiles on bangalore5
I have only been able to uncompress by logging in as root
on bangalore5
Login as root to bangalore5
bang5# cd /india2/projects/du/Displays_Test/sourcefiles/MD90/m902005
bang5# uncompress m902005.tar
bang5# tar xvf m902005.tar
bang5# rm m902005.tar
Remove the tar file after you extract all the sourcecode. There
is no reason to have to keep it laying around. This final step
makes available all of the source files for the m902005 build.
BUILD
To download the swit502 software, I did the following steps:
1) $ diff b3845np:acm_config_contents.txt b3850np:acm_config_contents.txt
/output=diff.txt
2) Hand edit diff.txt to include only the changed code packages and
to put diff.txt into a format similar to the original
acm_config_contents.txt.
3) $ rename diff.txt acm_config_contents.txt
4) $ @ebwr3:[birks.hiso_tools]createfetch ---> creates fetch.acm
5) Log onto V-node for b737-800 src access to acm
6) $ b737srcacm
7) acm> @fetch.acm --> obtains copies of changed files from ACM
8) ftp> cds06
9) ftp> mput *.ada --> copies .ad files to the sun
10) login to sun
11) % tar cvf b38swit502.tar *.ada
12) compress b38swit502.tar
13) ftp 204.220.167.31
14) ftp> cd /india3/737_800/sourcefiles/b38swit502
15) ftp> bin
16) ftp> put b38swit502.tar.Z
17) login to bangalore5
18) bang5> cd /india3/737_800/sourcefiles/b38swit502
19) bang5> uncompress b38swit502.tar
20) bang5> tar xvf b38swit502.tar
BUILD
To download the new non-partition build, I did the following:
1) $ integ b737 -- to define logicals
2) $ set def b3860np
3) $ ftp cds06
ftp> put b800_np_driver.pth b38swit601.pth
ftp> bin
ftp> put b800_np_driver.abs b38swit601.abs -- unique build name
4) logon to Phoenix sun
5) % tar cvf b38swit601.tar b38*.*
% compress b38swit601.tar
6) ftp 204.220.167.32
ftp> cd /atsd/projects/du/Displays_Test/SUT
ftp> bin
ftp> put b38swit601.tar.Z
7) logon to bangalore4
bang4> cd /atsd/projects/du/Displays_Test/SUT
bang4> su -- logon as superuser to do uncompress and tar
bang4> uncompress b38swit601.tar
bang4> tar xvf b38swit601.tar
BUILD
1) $ set def m9050502np
2) $ ftp bangalore4
ftp> cd /india4/projects/du/Displays_Test/SUT
3) ftp> bin
ftp> put md90_np_driver.abs m9050502.abs -- you need to rename
-- since every np build
-- has the same filename
4) ftp> ascii
ftp> put md90_np_driver.pth m9050502.pth
5) send e-mail to notify everyone of new build.
back
