Packaging

Installation

There are three main ways to deploy guibot on your platform: a platform-independent way through PyPI as well as platform-specific ways through a RPM or Debian package. As a platform specific approach for Windows, you just need to find the required executables for the backends dependencies most of which are fully available as well.

In order to build an RPM/Debian package, you have to clone the repository

git clone --depth 1 https://github.com/intra2net/guibot

or to download the most recent release tarball. All packaging commands assume you are running from within the guibot folder and the same applies to installing additional PyPI dependencies.

PyPI

To install guibot simply tun

pip install guibot

This will install only the most important dependencies leaving the optional ones out. To install all backend dependencies run the following within the guibot folder

pip install -r packaging/pip_requirements.txt

Depending on your choise of OS these requirements might have dependencies that are outside of the scope of pip. We provide an example script for RPM-based systems that you can also consult for any potential missing dependencies for your system of choice:

bash packaging/packager_pip.sh

Only Python 3 is supported and Python 2 support was deprecated in 2018.

NOTE: The PyPI OpenCV version with contribution modules does not support text matching so you will need an official RPM/Debian package for it.

RPM package

You can build an RPM package with

bash packaging/packager_rpm.sh

or simply view the contents for RPM requirements for running as well as building split into the respective stages.

Debian package

You can build a Debian package with

bash packaging/packager_deb.sh

or use it in the same way as the RPM packager script.

NOTE: The Ubuntu OpenCV version is currently old and you need at least 3.0.0 to be able to use feature matching.