Installation via a Batch Script

You can install the product via a batch script, if desired.

Important: If running on Linux, use install.sh. For Windows versions, use install.bat .

Run the command ./install.sh

The values that control the installation are passed into the batch script as command line parameters, except for the Existing Installation Directory. The batch script gets the value for this from the $VOVDIR environment variable as it runs.

Only the New Installation Directory value is a required parameter. The batch install uses a default value for the other fields.

Because this is a new install, the option -local create should be used for specifying the handling of the "local" directory.

Here is the logical description of calling the batch install for the scenario of installing for the first time.

% cd /usr/tmp/rtda_download 
% ./install.sh //opt/altair/vov/1212.1.0 -local create -rlm <port@host> -plat '<platform list>'

Here is a specific example of installing for the first time that compares to the example used in the GUI dialog example above.

% cd /usr/tmp/rtda_download 
% ./install.sh //opt/altair/vov/1212.1.0 -local create -rlm 7070@buffalo; -plat 'linux'

install.sh

This script supports batch installation on Linux as well as Windows. Run from the directory where the installation files were extracted.

By default, the installer will run in graphical mode. Use the -batch option to suppress the GUI and run in batch mode.

Usage

./install.sh [INSTALLPATH][OPTIONS]

Options

Use the options below for non-interactive installation.

-alm PORT@HOST

Value to use for ALTAIR_LICENSE_PATH.

-batch

Install in batch mode. If INSTALLPATH is not passed as an argument, the default installation path for Linux is /opt/altair/vov/1212.1.0 and for Windows is C:/altair/vov/1212.1.0.

-local HANDLING

Specify handling of the 'local' directory where HANDLING is one of the following. See the description of "previous installation" below:

copy: Copy previous installation's local directory if it exists. If not, create a new version-specific local directory. This is the default behavior for Windows.
create: Create new version-specific local directory.
link: Link to previous installation's local directory. If no previous installation exists, a version-specific copy is installed.
linkext: Link to a version-independent local directory one level up. This mode results in the local directory being placed in the parent of the installation directory, and a symbolic link is created inside the installation to point to it. If a version-independent local directory already exists from a prior installation, it is unchanged. If a previous installation exists, the local directory is copied from the previous installation. If no previous installation exists, a new local directory is created. This facilitates the reuse of the local directory for all installed versions. This is the default handling for Linux. Not supported on Windows.

The default handling for Linux is linkext, which results in the local directory being placed in the parent of the installation and a symbolic link created inside the installation to point to it. This facilitates the reuse of the local directory for all installed versions.

The default handling for Windows is copy. Only copy and create are supported on Windows.

-nocommon

Used when installing additional platforms after an initial installation has been performed, to prevent overwriting of the common directory. Ignored on Windows.

-noconfirm

Do not prompt for confirmation to begin the installation process when running in batch mode.

-platforms LIST

A quoted, space-separated list of platforms to install. Supported platforms are: armv8, linux64, and win64. Defaults to the platform on which the installer is run.

-previous PATH

Path to previous installation, if applicable. Defaults to the value of $VOVDIR if set in the calling environment. Otherwise, defaults to an empty string.

Examples

./install.sh /opt/altair/vov/<version>
./install.sh /opt/altair/vov/<version> -alm 6200@almsrv
./install.sh /opt/altair/vov/<version> -alm 6200@almsrv -batch
./install.sh /opt/altair/vov/<version> -local create -alm 6200@almsrv
./install.sh /opt/altair/vov/<version> -local link -platforms 'linux64 win64'

Because this is an update install to add a new platform to a previously installed release, the options -nocommon and -local copy should be used. The copy choice for the local parameter will cause the process to copy the local files onto themselves, creating a non-destructive no-op operation.

Here is the logical description of calling the batch install for the scenario of adding platform-specific files for a new platform.

% cd /opt/altair/vov/2023.1.0 
% ./install.sh /opt/altair/vov/2023.1.0 -nocommon -local copy <port@host> -platforms '<added-platform>'

Here is a specific example of doing an update by running the batch install to add the platform Linux to the release.

% cd /usr/tmp/altair_download 
% ./install.sh /opt/altair/vov/2023.1.0 -nocommon -local copy -alm 6200@almsrv; -platforms 'linux64'

Sample Module - Software Environment Management

If your company uses the "Modules" software from http://modules.sourceforge.net/ to manage the environment for the installed tools, the installation script also generates a module file named vov.modulefile to copy into one of the directories of your MODULEPATH where other tool environments are stored.

For example:

% mkdir -p /tools/modules/3.2.8a/Modules/modulefiles/vov
% cp /opt/altair/2023.1.0/common/etc/vov.modulefile /tools/modules/3.2.8a/Modules/modulefiles/vov/2023.1.0

% module avail
---------- /tools/modules/3.2.8a/Modules/modulefiles ----------
vov/2023.1.0      vov/2022.1.1