There are 2 supported mechanisms for using the Geosoft GX API in an external application. The first (default) mechanism relies on an existing installation of Geosoft Desktop Applications being installed on the system. The second mechanism requires the installation and setup of a redistributable package. Each is described in a separate section below.
...
Applications that use this mechanism requires either Geosoft Viewer or Oasis montaj installed. A handful of thin wrapper dlls need to be placed next to your application binaries. These dlls take care of the redirection of API calls to the desktop platform where the functionality is implemented. The versioned redist dlls are available in the GeosoftInc/gxcore Github repository.
The API is serviced from the application via a number of small wrapper dlls. Under normal circumstances this is all that should be needed for the system to work. The default "Core" Geosoft registry keys (under HKEY_LOCAL_MACHINE\SOFTWARE\Geosoft) will be read to detect the location of the application binaries. If not a geosoft.key text file can be placed next to the dlls. This file should contain a single line containing the alternative registry key. Usually this will be done to target a Geosoft Beta or Pre-Release instance.
...
Standalone Use via GXPY
In version 9.5 6 the gxpy Python setup.py mechanism has been modified to automate the configuration of a local Python environment to use one of the standalone redistributable packages instead of a Geosoft Desktop Applications instance. To do this follow the following steps:
...
changed (compared to the 9.5 mechanisms). Instead of using the 'python setup.py install' mechanism to embed the redistributables the module can be installed using the standard mechanism and the standalone paths can be configured at runtime via new parameters passed to the gxpy.gx.GXpy constructor: