Quick start

The basic usage of the Software Manager is straightforward.

Using SOM in the browser

1. Run the accompanying binary som (MVTec Software Manager).
   If your browser does not come up, start MVTec Software Manager CLI, enter som, and use the displayed address in any HTML5-compliant browser on your system.

2. Select the Available page.

3. To install a software product, click its Install button.
   ⤷ The recommended packages are pre-selected.
   Alternatively, click Select Packages to select a custom set of packages from scratch.
4. Click Apply to start the installation.

More Info

For detailed information, see Using SOM with the GUI (browser).

Using SOM via the command line

Installing a product via the command line looks like this:

./som install -f <product feed> <package> --accept <EULA hash>

To create this command, do the following:

1. List all available products:

   ./som available
   

2. List all available packages for a given product:

   ./som list -f <product feed>
   

   <product feed> has to be one of the feeds you received from the previous command.

   Tip

   You can also use only a part of the feed’s string, for example: halcon-23.05-progress instead of https://packages.mvtec.com/halcon/halcon-23.05-progress/halcon-23.05-progress.feed.

3. Run the following command to start the process of installing a product:

   ./som install -f <product feed> <package>
   

   <package> has to be one of the packages or meta packages from the previous command (for example, dev or rt for installing HALCON Development or HALCON Runtime, respectively).
   ⤷ The Software Manager prints the EULA to standard out.

4. To accept the EULA and actually install the product, run the install command again with the EULA accept flag:

   ./som install -f <product feed> <package> --accept <EULA hash>
   

   This command is also shown at the end of the EULA output.

More Info

For detailed information, see Using SOM from the command line.

About offline usage

Once a particular package has been downloaded, it is kept in a local repository, and it can be installed without requiring an internet connection.

Depending on the amount of installed software packages, the repository may grow quite large over time. The contents can safely be deleted if disk space becomes an issue. Missing packages will be downloaded again if required unless they are no longer provided at the remote catalog URL.