# Installing eVision

## Installing eVision on Windows

**eVision** comes as a single installer package `evision-win-26.10.0-beta.2.dev.exe`. It contains everything needed to run or develop applications using **eVision**, except for the Deep Learning redistributables (required for GPU support and accelerated inferences using third party engines) that comes in the installer package `evision-win-deep-learning-redist-26.10.0-beta.2.dev.exe`.

Several other installers containing a part of **eVision** are also available.

### Installation Types

The **eVision** Installer provides the following installation types:

* `Complete`: everything needed for running or developing applications is installed on the system.
* `Runtime`: installs all binaries needed to run applications using **eVision** on the system.
* `Studio`: installs everything needed to run the **Studio** applications of **eVision**.
* `Custom`: allows to select exactly what components are installed on the system.

### Older Versions

**eVision** does not replace other **eVision** versions but installs alongside them. Only maintenance releases (with the same major and minor versions but a different revision number) automatically update an existing installation.

### Command-Line Interface

To install **eVision** with the command line, use:

* `evision-win-26.10.0-beta.2.dev.exe -silent INSTALLTYPE=[install_type]`
  * Where `[install_type]` can be `Complete`, `Runtime` or `Studio`.
  * By default, installation type is `Complete`.
* For the command prompt to wait for the end of the installation add `start /wait` at the start of the command:
  * `start /wait "evision-win-26.10.0-beta.2.dev.exe -silent INSTALLTYPE=[install_type]"`

### Installation Logs

* By default, the **eVision** installer generates installation log files in the `%LOCALAPPDATA%/Temp` directory.
* If you want the installer to generate the installation logs somewhere else, use the following command:
  * `evision-win-26.10.0-beta.2.dev.exe -log [logFilename]`
  * Where `[logFilename]` indicates where the main installation log is saved.
  * Additional log files may be created along the main one, their name is derived from `[logFilename]`.

## Installing eVision on Linux

There are 3 archive files provided for the Linux operating systems:

* `evision-linux-26.10.0-beta.2.dev.tar.gz` contains the **eVision** libraries and the **Neo License Manager**.
* `evision-deep-learning-redist-linux-26.10.0-beta.2.dev.tar.gz` contains the Deep Learning redistributables for GPU support and accelerated inferences with third party engines.
* `neo-linux-license-manager-*.tar.gz` contains only the **Neo License Manager**.

#### NOTE
The packages are available in `deb` and `rpm` formats, for Intel x86-64 and ARM64 architectures.

### Supported Distributions

The supported distributions are available in the [Release Specifications](../release_notes/26.10/release_specifications.html.md) section of the [Release Notes](../release_notes/26.10/index.html.md) and in the `README` file available in **eVision** installers.

### Installing the eVision Library and the Neo License Manager

The installation procedure is documented in the `README` file that comes along the installation archive files of **eVision**.

### Configuring the Environment

In order for a program using **eVision** to work correctly, configure its environment using:

```bash
(bash)
# source /opt/alliedvision/eVision_26_10/prepare_evision_environment.sh
```

#### NOTE
This command effects are not persistent. The command sets up the environment only for the current shell session.

## Retrieving the Installation Folders Programmatically

See [Retrieving the Installation Folders Programmatically](../using/basic_operations/utils/retrieving_the_installation_folders_programmatically.html.md)

## Checking the Health of your eVision Installation

* **eVision** provides you with a way to validate your **eVision** installation via the health check commands embedded in the following applications:
  * **ev_helper** (in the directory `bin`): Use its health check to check the correct installation of the **eVision** libraries.
  * **eVisionStudio** (in the directory `eVisionStudio`): Use its health check to check the correct installation of the **eVision Studio** and its dependencies.
  * **DeepLearningStudio** (in the directory `Deep Learning Studio`): Use its health check to check the correct installation of the **Deep Learning Studio** and its dependencies.
* To perform a health check:
  * Call the application with in the command line with the command `health_check` (for ex. `ev_helper health-check`).
  * If the call returns 0, the health check is successful and the installation is validated.