$! Define the editor
$ eve == "spawn/nowait edit/display=decwindows/tpu"
$ eve filename.txt
Compiler:
$! Define the compiler
$ C64 :== CC/POINTER_SIZE=64/check=pointer=all/optimize=(tune=ev6,level=5)
$! Compile the program 'ipl_scanco_c' and link it to existing libraries
$ c64 ipl:ipl_scanco_c
$!
$ link /exe=ipl:ipl_SCANCO_c -
ipl:ipl_scanco_c, -
ipl:ipl_scanco_c_ident/opt, -
ipl:ipl_proc/lib, -
ipl:ipl/lib, -
mu:scanco_ext/lib, -
dsrc:d3p_scanco/lib, -
scanco_lib/lib
SCTHIN (DS10L)
duck.kin.ucalgary.ca has been assigned IP address 136.159.130.33
netmask 255.255.255.0
default router 136.159.130.34
DNS servers 136.159.130.130, 136.159.130.3
Login microct or devel with not2lame.
To boot into the cluster
>>>boot ewa0
To boot out of the cluster, unplug the ethernet cable and
>>>boot
To get to boot prompt, type shutdown on the login screen. Or, after powerdown, hit ctrl-P repeatedly.
You will need a C compiler on OpenVMS. There are several versions of CVS available, but all of them need some tweaking before they can be successfully built.
This will create .cvspass file in your home directory so your only
need to use the cvs login once
$ cvs co "vtknew"
public.kitware.com has ip address 66.194.253.19
Update VMS licenses
As user system:
$ lic list/full
and check which licenses are currently from 'MONTAGAR' and expire on Aug 31.
I recommend to only then replace those licenses with the new ones, and not load the whole license text file that you get from HP. Make a 'shortlist' of the licenses you need, then FTP them to the VMS system and copy and paste.
Layered Products (any licence, but NOT the openvms-Alpha itself!)
Then, on SCTHIN, for the basic 'openvms-alpha' license itself. In a cluster, this license must be limited to one computer only, so first, to delete the correct of the multiple openvms-alpha licenses only. If I ever wanted SCTHIN to be the server in a cluster, I should do the following (very unlikely!):
$ lic list openvms-alpha/ful
$ lic delete openvms-alpha/auth=xxxxxx
! after first looking up the authori. of that montagar license.
$ LICENSE REGISTER OPENVMS-ALPHA -
/ISSUER=MONTAGAR -
/AUTHORIZATION=EDU-742405-743161 -
/PRODUCER=DEC -
/UNITS=0 -
/TERMINATION_DATE=31-AUG-2008 -
/ACTIVITY=A -
/OPTIONS=(NO_SHARE) -
/CHECKSUM=2-JMOA-GOFL-AKID-DHCJ
$ lic modify openvms-alpha/auth=EDU-742405-743161/include=scthin
! to make it available to scthin only.
You will be prompted for your password to access the machine
Wait for checkout to complete
Build ITK using Cmake
a. Open Cmake
b. Choose C:\pack\InsightToolkit-2.8.1 as source code
c. Make C:\pack\ITK binary code location
d. Click ‘Configure’ and choose desired compiler
e. Use the following Cache values:
BUILD_EXAMPLES: ON
BUILD_SHARED_LIBS: ON
BUILD_TESTING: ON
BUILD_BACKWARDS_COMPATIBILITY: 2.4
CMAKE_INSTALL_PREFIX: C:/Program Files/ITK
f. Click ‘Configure’, all red values should turn grey
g. Click ‘Ok’, wait as Cmake will close automatically
Build VTK using Cmake
a. Open Cmake
b. Choose C:\pack\VTK-2006-09-01 as source code
c. Make C:\pack\VTK binary code location
d. Click ‘Configure’ and choose desired compiler
e. Click the ‘Show Advanced Values’ checkbox and verify the following settings, all others can be left as defaults:
BUILD_EXAMPLES: ON
BUILD_SHARED_LIBS: ON
BUILD_TESTING: ON
BUILD_BACKWARDS_COMPATIBILITY: 2.4
CMAKE_INSTALL_PREFIX: C:/Program Files/VTK
VTK_USE_ANSI_STDLIB: ON
f. Click ‘Configure’, all red values should turn grey
g. Click ‘Ok’, wait as Cmake will close automatically
Install Qt 3.3.6 Academic version
a. Run “qt-win-academic-3.3.6.exe”
b. When asked for license information choose to use license file and open “qt-license-3.3.6”
c. For installation options use defaults and be sure to build with shared libraries in Step 8 File:QtOptions.jpg
Build vtkMy using Cmake
a. Open Cmake
b. Choose C:\pack\vtkMy\src as source code
c. Make C:\pack\vtkMy\bin binary code location
d. Click ‘Configure’ and choose desired compiler
e. Click the ‘Show Advanced Values’ check box and verify the following settings, all others can be left as defaults:
BUILD_APPLICATIONS: ON
BUILD_SHARED_LIBS: ON
BUILD_TEST_PROJECTS: ON
BUILD_BACKWARDS_COMPATIBILITY: 2.4
CMAKE_INSTALL_PREFIX: C:/Program Files/VTKMY
USE_ITK: ON
USE_QT: ON
USE_FLTK: OFF
VTK_DIR: C:/pack/VTK
ITK_DIR: C:/pack/ITK
f. Click ‘Configure’, all red values should turn grey
g. May have to click configure again if any red values are still present
h. Click ‘Ok’, wait as Cmake will close automatically
Build VTK using Visual C++ 6.0 (or desired program)
Open C:\pack\VTK\vtk.dsw
Click ‘Build’
Build ITK using Visual C++ 6.0 (or desired program)
a. Open C:\pack\ITK\itk.dsw
b. Click ‘Build’
Build vtkMy using Visual C++ 6.0 (or desired program)
a. Open C:\pack\vtkMy\bin\vtkmy.dsw
b. Click ‘Build’
WinCVS and PuTTY for vtkMy
NOTE: An alternative CVS client has been suggested, but not tested:
SmartCVS from www.syntevo.com with a foundation license.
Setting up WinCVS to use PuTTY is fairly straightforward, but does require a few configuration settings in addition to installing the software. You can do it with the following steps.
Follow menus: Start/Programs/PuTTY/PuTTYgen From the PuTTY Manual:
...press the "Generate" button and PuTTYgen will begin the process of actually generating the key.
First, a progress bar will appear and PuTTYgen will ask you to move the mouse around to generate randomness. Wave the mouse in circles over the blank area in the PuTTYgen window, and the progress bar will gradually fill up as PuTTYgen collects enough randomness. You don't need to wave the mouse in particularly imaginative patterns (although it can't hurt); PuTTYgen will collect enough randomness just from the fine detail of exactly how far the mouse has moved each time Windows samples its position.
When the progress bar reaches the end, PuTTYgen will begin creating the key. The progress bar will reset to the start, and gradually move up again to track the progress of the key generation. It will not move evenly, and may occasionally slow down to a stop; this is unfortunately unavoidable, because key generation is a random process and it is impossible to reliably predict how long it will take.
When the key generation is complete, a new set of controls will appear in the window to indicate this.
Set the key comment and password. Set the key comment to your email address by typing it into the "Key Comment" box. Set the password by entering it twice, once in the "Key passphrase" box and once in the "Confirm Passphrase" box.
Save the keys: save the public key on your desktop as identity.pub and the private one as identity.ppk
Email the identity.pub file as an attachment to skboyd@ucalgary.ca and ask for it to be added to the .ssh/authorized_keys file for your cvs repository. Please specify which repository you are requesting access to in the e-mail (i.e., vtkMy).
Setup environment variables
Choose Menus: Start/Settings/Control Panel
Double click on the "System" Control Panel
Pick the "Advanced" tab and pick "Environment Varibles..."
Add User environement variables
- Add PLINK_PROTOCOL value "ssh"
- Add CVS_RSH value "plink"
- Edit or Add PATH appending value ";C:\Program Files\PuTTY"
In WinCVS, bring up the "Preferences" dialogue box from the Admin menu
In the "General" tab put in your CVSROOT value, (i.e. :ext:myusername@m177.enme.ucalgary.ca:/localhost/cvsroot) File:Wincvs general.jpg
Switch to the "Ports" tab.
Tick the box there labelled "Check for an alternate rsh name" and in the text entry field to the right enter "plink". File:Wincvs ports tab.jpg
Select "OK" on teh "Preferences" dialogue box.
Once you've heard back from the administrator (skboyd) that your ssh keys have been added, test your putty key configuration:
Double click on "identity.ppk" on your desktop. If this doesn’t start pagaent.exe automatically, then manually start the program from the directory you installed putty.exe.
If your identity file isn't already loaded, you will be prompted for the password you entered in step 4.
The Pageant icon (a little PC with a hat) should appear in the bottom right menu bar.
You should now be able to use WinCVS to access the repository, with a secure connection whenever Pageant is running. You can start Pageant by double-clicking on your identity.ppk file.
Setting up CVS access from Linux/Unix
To understand the codes for a CVS update, see page 121 of CVS users guide, section A.16.2.
eval `ssh-agent` {use the funny back single quotes}
Remotebox:
cat identity.pub >> ~/.ssh/authorized_keys
To avoid writing your passphrase every time you log on, run:
ssh-add
Should work if ssh-agent is already running (eval `ssh-agent` in the .bashrc file).
Do the following to limit access to cvs for the users:
edit the public key installed in the .ssh/authorized_keys file with the following at the beginning of the public key line:
command="/usr/bin/ssh server"
NOTES ABOUT KEYS
Remember, the "authorized_keys" file is a concatenation of public (id_rsa.pub) keys,
and the "id_rsa" is the private key.
Every user on every computer should only have ONE "id_rsa" file,
but can have multiple "id_rsa.pub" files concatenated into
their "authorized_keys" file.
Using CVS from a command line
To find a difference:
$ cvs diff mylocalfile.cxx
To add a new file:
$ cvs add mynewfile.cxx
$ cvs commit mynewfile.cxx
To update local file:
$ cvs update -dCP
or
$ cvs update -dCP myfile.cxx
To check if a more recent version is available:
$ cvs diff myfile.cxx
or
$ cvs update
To update CVS repository:
$ cvs commit mylocalfile.cxx
Add a project to vtkMy
Add a new project directory in the vtkMy/src/Applications directory.
Update the CMakeLists.txt file in /src/Applications to include the new directory in the SUBDIRS() list.
Copy the CMakeLists.txt and source code files from an existing project such as AppMohr and put them into the new directory. These files can be edited for your new project.
Edit the copied CMakeList.txt file and the change the name of the .cxx to the name of the new project.
Run CMake, taking the source code from vtkMy/src and building the binaries in vtkMy/bin.
Open the Visual C++ workspace and edit the source code (since at the moment it will be a duplicate of whatever project you copied in step 3).
Compile your new code. Usually, all the development should be done in the “Debug�? mode (rather than “Release�?, etc.).
If, to run your application, you need to include command line arguments, go to the menu item [Project][Settings], and on the ‘debug’ tab set the Program Arguments as shown.
You would run this script called faim.com as follows
$ faim.com inputfile
Sample 4
This example uses two files. One called wrap.com is the base program that is called in
a more general program called wrap_all.com so that many different files can be processed
by the base script.
I include in the attachments my checklist I use for a Solaris 10
installation, adjusted to show only items particular to yours
and not my entire decision tree. I added brief explanations
for some of the items that might seem arbitrary otherwise.
Very similar decisions are made when installing any release
of Linux, Solaris, MS Windows or yet another operating
system - the details vary though.
However, I would not install both Emacs and XEmacs at the same
time. Nowadays, I highly recommend installing only one of them,
with my preference given to XEmacs. Of course, only when
there are no specialized Lisp packages that require Emacs.
Then my installation would be like below:
$ cd /cdrom/s10_software_companion/components/sparc/Packages
$ cat > /tmp/nointeraction
mail=
instance=unique
partial=nocheck
runlevel=nocheck
idepend=nocheck
rdepend=nocheck
space=quit
setuid=nocheck
conflict=quit
action=nocheck
basedir=default
$ pkgadd -a /tmp/nointeraction -d . -n SFWbdb SFWgcc34l SFWxmacs
[ Copyright and legal notices omitted for brevity. ]
21872 blocks
Installation of <SFWbdb> was successful.
[ Copyright and legal notices omitted for brevity. ]
69953 blocks
Installation of <SFWgcc34l> was successful.
[Copyright and legal notices omitted for brevity. ]
264202 blocks
Installation of <SFWxmacs> was successful.
$ emacs () { /opt/sfw/bin/xemacs $* ; }
$ pkgadd -a /tmp/nointeraction -d . -n SFWddd SFWgbin SFWgdb
[ To complete installation of the other packages you require. ]
$ pkginfo SFWbdb SFWddd SFWgbin SFWgcc34l SFWgdb SFWxmacs
system SFWbdb berkeleyDB - Berkeley Database Library
system SFWddd ddd - GNU Data Display Debugger
system SFWgbin binutils - GNU binary utilities
system SFWgcc34l gcc-3.4.2 - GNU Compiler Collection Runtime Libraries
system SFWgdb gdb - GNU source level debugger
system SFWxmacs XEmacs - text editor
