This section describes operating system and compiler details for supported UNIX platforms. Disk space and compiler requirements for each are described below.
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.
ST-Developer for 32bit Linux runs on Linux distros with glibc v2.3.4 or later and a compatible version of GCC. This covers distros that support Linux Standard Base (LSB) 3.x or better. This includes distros running glibc 2.3.4 (RedHat Enterprise Linux 4, Fedora 4, SuSE 9, Gentoo 2004.3, Ubuntu 5.10-6.10), glibc 2.5 or newer (RedHat Enterprise Linux 5, Fedora 6-13, SuSE 10-11, Gentoo 2007-2010, Ubuntu 7-10). To find your C runtime version, run "ldd --version".
The ST-Developer libraries are built for GCC 3.4 and the newer 4.x series of releases, which is compatible with the GCC versions included with all of the distros discussed above. To see your GCC version, run "gcc --version".
ST-Developer for 64bit Linux has the same version requirements for glibc and GCC, so it will run on the 64bit version (x86_64 processor architecture) of any LSB 3.x or better distro, such as Red Hat Enterprise Linux 4 and 5, Fedora 4-13, SuSE 9-11, Gentoo 2004-2010, or Ubuntu 5-10.
The 32bit Linux installation requires about 1.6 gigabytes of disk space while the 64bit version requires 2 gigabytes of space. After installation, you can reduce disk usage by removing any unneeded library versions under the lib directory.
ST-Developer for IBM POWER-series (System P) requires AIX 5.3. The distribution contains versions of the C++ programing libraries built for use with the IBM XL C/C++ compiler (xlC). Four versions are provided covering all combinations of default and 64bit architecture linkage, with and without thread-safe options (xlC_r).
The AIX installation requires 3 gigabytes of disk space. After installation, you can reduce disk usage by removing any unneeded library versions under the lib directory.
ST-Developer for Hewlett Packard Itanium requires HP-UX 11. The distribution contains versions of the C++ programing libraries built for use with the ANSI C++ compiler in 64-bit mode (aCC +DD64) with default linkage as well as position-independent code (+Z +z -mt) link options.
The HPUX Itanium installation requires 5.6 gigabytes of disk space, After installation, you can reduce disk usage by removing any unneeded library versions under the lib directory.
ST-Developer for Solaris x86 and ST-Developer for Solaris SPARC can be used with Solaris 10 and later. Each contains versions of the C++ programing libraries built for the Sun Studio 11 C++ compiler. Four versions are provided covering all combinations of default and 64bit architecture linkage, with and without the position-independent code (-PIC -mt) compile option.
The Solaris x86 installation require 2.3 gigabytes of disk space, and the Solaris SPARC installation requires 2.4 gigabytes of space. After installation, you can reduce disk usage by removing any unneeded library versions under the lib directory.
- Mount the ST-Developer CD-ROM and cd to your desired
installation directory. Suggestions for mounting CD-ROMs on various Unix systems
are available if you need assistance mounting the disk.
- Use unzip to extract from /cdrom/stdev.zip. This will
create a directory called steptools_15. 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_15 directory and run the stdev_install script. This will verify the install location as well as some information about the C++ compiler.
- Request, and then install a license key as described in Software License Keys. We will send the key by e-mail.
% cd steptools_15 % ./stdev_install
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.
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 variables are correct then add the settings to your environment.
Next, 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
- 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 /usr/local/steptools_15/runtime/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 (AP203, AP214, 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.