6.1 Platform Requirements
This section describes operating system and compiler details for supported UNIX platforms. Consult the README file on the CD for exact disk space requirements and other installation details.
Some C++ compilers require flags or other special treatment. This is handled by makefile definitions in the $ROSE/config directory. Makefiles include one of these configuration files through the $ROSE_CONFIG environment variable. The settings are normally handled by the ST-Developer installation script.
Linux Notes
ST-Developer for Linux will run on a wide variety of Linux distributions. The basic requirement is glibc v2.3.2 or later and a compatible version of GCC. This should be satisfied by any distribution compliant to Linux Standard Base (LSB) either 2.x or 3.x. The executables will work on older distros running glibc 2.3.2 (such as RedHat 9 and RHEL3, Fedora Core, SuSE 8.2/9.0, Debian 3.1, Gentoo 1.4/2004.1, Linspire 4.5/5.0), newer versions running glibc 2.3.4 (RHEL 4, Fedora 4, SuSE 9.3, Gentoo 2004.3, Ubuntu 5.10), and glibc 2.5 (RHEL 5, Fedora 6-7, SuSE 10.2, Gentoo 2007, Ubuntu 7.04). To see what your system has, run " ldd --version ".
The ST-Developer libraries are built for use with several versions of GCC. If you look under the ST-Developer lib directory you will see several versions. The linking conventions change between GCC 3.2/3.3 and the latest GCC 3.4/4.x compilers, so make sure that you link against the correct ones for your compiler. To see what GCC version your system has, run " gcc --version ".
Hewlett Packard PA-RISC / HPUX Notes
ST-Developer for Hewlett Packard PA-RISC requires HP-UX 11. The installation is compatible with the 9000 Series 700 PA-RISC 1.1 machines as well as the newer C-series PA-RISC 2.0 machines. The C++ programing libraries are built for use with the HP ANSI C++ compiler ( aCC ).
Silicon Graphics / IRIX Notes
ST-Developer for Silicon Graphics can be used with IRIX 6.2 and later. The C++ programing libraries are built for use with the SGI MIPSpro C++ compiler.
Sun SPARC Notes
ST-Developer for Sun SPARC can be used with Solaris v7 and later. The distribution contains versions of the C++ programing libraries built for use with Forte and Sun Studio C++ (Sun Workshop 5.0, Forte Developer 6, Sun Studio 7 to 11), and the GNU GCC v3.4/4.x compilers.
6.2 Installation Procedure
- Mount the ST-Developer CD-ROM and cd to your desired installation directory. See to Mounting CD-ROMs on Various Unix Systems if you need assistance mounting the disk.
Use unzip to extract from /cdrom/stdev.zip . This will create a directory called steptools_12 . A copy of the unzip program is included on the CD in the unzip directory. If several zip files are present, consult the README file on the CD to see which one to unpack.
In the following example, replace /usr/local with the install location and replace /cdrom with the actual CD mount point.
% cd /usr/local
% unzip /cdrom/stdev.zip
- Go into the steptools_12 directory and run the stdev_install script. This will verify the install location as well as some information about the C++ compiler.
% cd steptools_11
% ./stdev_install
- Request, and then install a license key as described in Software License Keys. We will send the key by e-mail.
ST-Developer is now installed. You can verify the environment settings on your machine and test the ST-Developer tools as described in the following sections.
Environment Settings
The install script creates a Rose_Logicals file in the ST-Developer installation directory with settings specific to your site. Check the file to make sure the following environment variables are set correctly:
ROSE ST-Developer installation directory.
ROSE_BIN Directory containing executables. Usually $ROSE/bin . Put this in your shell search path.
ROSE_INCLUDE Directory containing the ST-Developer C++ header files. Usually $ROSE/include . Used by makefiles.
ROSE_LIB Directory containing the ST-Developer C++ libraries. Usually a subdirectory under $ROSE/lib . Used by makefiles.
ROSE_CONFIG Makefile configuration file in $ROSE/config that defines settings for your compiler and build options. This file is included by the makefiles for all sample programs.
ROSE_RUNTIME Optional. Location of the ST-Runtime support files. If not set, tools look for $ROSE/runtime .
ROSE_LICENSE Optional. An alternate location for the license key file. If not set, tools look for $ROSE/license .
ST-Developer may include versions of the libraries built for different compilers or link options. The $ROSE_CONFIG and $ROSE_LIB variables are set by the install script to your default choice, but you can change them later if you need to use alternate library versions.
Verify the Installation
You can test the various components of ST-Developer using the following steps:
- Open the ST-Developer online manuals with your web browser. The manual home page is located at the following URL within the installation directory:
file:/<stdev_install_dir>/docs/index.html
- Start a new shell and evaluate the Rose_Logicals (csh) or Rose_Logicals.sh (bash) file to set the environment variables described above. Add $ROSE_BIN to your search path. Make sure these are always set before you use any of the ST-Developer tools.
% source Rose_Logicals
% set path=( $ROSE_BIN $path )
% . Rose_Logicals.sh
% export PATH=$ROSE_BIN:$PATH
- Use the rose file utility to list the installed system resource files. This verifies that the path and environment settings are properly configured. If you have problems, make sure that the $ROSE_BIN directory is in your search path
% rose ls
It should return something like the following:
Total number of designs:: 100
In C:\Program Files\STEP Tools\ST-Runtime 12\schemas\*.*
? ap239_product_life_cycle_support_mim_lf.rose
ap239_product_life_cycle_support_mim_lf_EXPX.rose
? associative_draughting.rose
associative_draughting_EXPX.rose
? automotive_design.rose
automotive_design_EXPX.rose
? building_design_schema.rose
building_design_schema_EXPX.rose
[ . . . files ommitted . . . ]
- Open the ST-Developer online manuals as described above. You will see a list of links to pre-installed schemas (AP201, AP202, etc). Go to one of them and compile one of the sample programs.
For each sample program you will see a Unix project link. Right-click on the link to save the project zip file. Unpack the zip file and compile the application by running make .
6.3 Mounting CD-ROMs on Various Unix Systems
STEP Tools CDs use an ISO 9660 filesystem, possibly with Rock Ridge extensions. The procedure for mounting CD-ROMs varies, so we have included instructions for some common platforms:
Linux
Simply insert the disk. On most modern Linux distros, it will be automatically mounted under /mnt/cdrom. If you have a different setup, you may need to manually mount the disk using a command like the following.
% mount -r -t iso9660 /dev/hdc /cdrom # IDE CD
% mount -r -t iso9660 /dev/scd0 /cdrom # SCSI CD
% umount /cdrom # to unmount the disk
Hewlett Packard PA-RISC / HP-UX
Using the sam system administration tool, invoke sam as root, navigate to Disk and File Systems , and then to File Systems . Under Actions | Add Local File System | Not Using The Logical Volume Manager , you will find a dialog box that mounts a CD as a one-time event.
If you know the device name, you can also mount the disk manually using:
% mount -r -F cdfs /dev/dsk/c1t2d0 /cdrom
% umount /cdrom
Where c1t2d0 is the actual device name of the CD-ROM drive.
Silicon Graphics/IRIX
Simply insert the disk. The system will automatically mount the disk as /CDROM . To unmount and eject the disk:
% eject /CDROM # to unmount the disk
Sun SPARC/Solaris
Simply insert the disk. The volume manager will automatically mount it under the /cdrom directory as:
/cdrom/<volumename> (such as /cdrom/cdrom0)
To unmount and eject the disk:
% eject cd