Installation
Install in one line
One script per platform. It downloads the driver, installs it per-user by default and registers the ADBC manifest so any client can load it by name.
1. Run the installer
Replace arrowtds with arrowfebe or arrowttc as needed. Use --system (with sudo or an elevated shell) for a machine-wide installation.
2. Load the driver by name
Because the installer registers an ADBC manifest, clients find the driver from its name alone — no path, no LD_LIBRARY_PATH.
Where things land
By default the installer places files per-user. The ADBC driver manager looks for manifests in the standard per-platform location.
| Platform | Driver files | ADBC manifest search path |
|---|---|---|
| Linux | ~/.local/lib/arpeio-adbc/ | ~/.config/adbc/drivers |
| macOS | ~/.local/lib/arpeio-adbc/ | ~/Library/Application Support/ADBC/Drivers |
| Windows | %LOCALAPPDATA%\arpeio-adbc\ | %LOCALAPPDATA%\ADBC\Drivers |
Point the driver at your licence
The installer accepts the licence three ways:
- A file path: --license /path/to/your.lic
- Inline text: --license-content "<licence text>"
- Environment variables: ARPEIO_ADBC_LICENCE_FILE or ARPEIO_ADBC_LICENCE
At runtime, drivers resolve the licence in this order:
- 1ADBC database options — arpeio.adbc.license or arpeio.adbc.license_file
- 2Environment variables
- 3An arpeio_adbc.lic file next to the driver
Useful commands
List the available drivers
Show what is already installed
Uninstall a driver
Supported platforms
The installers run on Linux (x64) and Windows (x64). macOS binaries are staged but not yet published.