Build Manager Installation

Users should begin by following the [common installation instructions] (Common-Install-Requirements) before proceeding to the buildmanager specific instructions below.

Third-party tools

The buildmanager has several dependencies on third party libraries which must be installed and available in the system path

  • Image Magick Starting with Nornir version 1.3.1 Image Magick version 7 or later is required. Previous versions of Nornir used Image Magick 6. The 16 bits-per-pixel version of Image Magick should be installed and in the system path. Q16 should be in the Image Magick download filename which indicates it is a 16bpp build. On Windows I use the shared library version (dll).

  • ir-tools The original NCRToolset, a.k.a. “ir-tools” are located at NCR Tools For Windows a somewhat optimized version is available. For Mac the version from Brad Grimm is required.

    The buildscripts were originally developed and used on Windows. They should work on on other platforms but are not tested. For Mac users I recommend using Mac Ports to install the numpy,scipy, and matplotlib libraries.

  • Optional: win32api

    As of version 1.0.1 the build manager will attempt to lower its priority below that of a normal process on the machine. This allows a machine to remain more interactive to users while doing builds. This requires the pywin32 package. Obtainable from Gohlke’s site.


There are many roads to installing the packages. One of these options should work. The alternatives are provided for troubleshooting

  1. Best option, use pip The simplest install is to go to the scripts directory for your python installation. C:Python27scripts is a common location. Install the nornir-buildmanager package directly from github via pip by typing the following command

    Pip has recently changed its behavior after version 1.4 to not install dependencies. Using PIP 1.4 this command should be sufficient to install nornir.:

    pip install git+ --upgrade

    Later versions of Pip require each package to be installed separately.:

    pip install git+ --upgrade
    pip install git+ --upgrade
    pip install git+ --upgrade
    pip install git+ --upgrade
If you are on a machine that can build C extensions for Python packages, for example a working Mac Ports install, the above approach should work even if one hasn’t manually installed the ore-requisite packages.
  1. Second option, use git and

    Open a command prompt “cmd.exe” and create a directory to store github code in. I use _C:srcgit_.
    1. Change to this directory:

      cd \src\git
    2. Download the source:

      git pull
    3. Install the package:

      python install
  2. Manual Option:

    Download the repository as a .zip file . If you want to change the source you should create a Github account, clone the repository, and work from that version. Instructions for using git are beyond the scope of this installation manual. A good starting point for learning about git is Pro Git by Scott Chacon.

    Extract the source code to a directory on your local file system. In this example I will use C:srcgitnornirnornir-buildmanager

    Open a console. It is a good idea to start a new console to ensure all of the changes to the system path are active. Change to the directory you extracted the nornir-buildmanager into and run the python install command, ex::

    C:srcgitnornirnornir-buildmanager>python install


To be thorough I suggest uninstalling the previous nornir version using pip:

pip uninstall nornir-buildmanager
pip uninstall nornir-imageregistration
pip uninstall nornir-pools
pip uninstall nornir-shared

After uninstalling the old version follow the installation instructions above.

If installation fails scan the output for evidence of a missing package that could not be installed. The biggest cause of problems during an upgrade is nornir requiring an updated version of a library that PIP is unable to build locally. For example Scipy, Numpy, or Matplotlib. This will cause the automated setup to fail. In these cases the best approach is to locate the latest versions of those packages, uninstall the old version, install the new version, and then attempt the installation again.