Clone this wiki locally
This page represents installation layout on a Linux system.
- jackd - classic JACK launcher executable
- jackdbus - D-Bus JACK service (installed if D-Bus integration is built)
- examples clients
They are installed in
libjack and libjackserver are installed in
libtool-like install is made with .la files and symbolic links, like this:
libjack.la libjack.so --> libjack.so.0.0.28 libjack.so.0 --> libjack.so.0.0.28 libjack.so.0.0.28
jack drivers are installed into
in-process clients are installed into
D-Bus service file
If jackdbus is being installed, D-Bus service is installed too. This file instructs D-Bus session bus how to activate JACK controller object upon request.
By default org.jackaudio.service file is installed in
However user may force using real D-Bus service directory by specifying --enable-pkg-config-dbus-service-dir
<PREFIX>/share/dbus-1/services/ will differ from one specified in pkg-config file of D-Bus when they are installed in different prefixes. If service file is installed in different prefix, D-Bus session bus daemon should be instructed to search in different directory (out of scope of JACK installation process, as implemented in distribution tarball).
They are installed in JACK specific header directory,
jack.pc is installed in
Man pages are installed in
HTML documentation is installed in JACK specific directory
Index is of the HTML documentation is within
Some unusual things related to installation relocatability:
- in-process clients and drivers are loaded from fixed path (
<PREFIX>/lib/jack/), specified literally during build. Drivers load directory may be overridden using JACK_DRIVER_DIR environment variable. ATM there is no way to override in-process client directory.
- D-Bus session bus daemon configuration may need modification to be able to auto-activate JACK controller service.
- jack.pc file contains