Parent: c2b9f357d52207ef22c9a4880cc0b5c7e8f11c5b
Author: Emil Velikov <emil.l.velikov@gmail.com>
Committer: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2024-02-20 15:51:26
Tree: 36368425b340ae154203e5733f0258aa497eaa82
build: handle relative libexecdir instances With earlier commit, we've used exec_dir to reference the path of obexd and bluetoothd within the service files. At the same time, in my testing I was providing the complete path on the configure command line. As result, things just worked. In the default case, the variable contains relative references to ${} variables, which as result end up literal in the services. Ultimately the service files were broken. Document are reuse the existing pattern of manually expanding the variables. Fixes: https://github.com/bluez/bluez/issues/736
Diffstat
| M | Makefile.am | | | 2 | +- |
| M | configure.ac | | | 18 | ++++++++++++++++++ |
| M | mesh/bluetooth-mesh.service.in | | | 2 | +- |
| M | obexd/src/obex.service.in | | | 2 | +- |
| M | obexd/src/org.bluez.obex.service.in | | | 2 | +- |
| M | src/bluetooth.service.in | | | 2 | +- |
| M | tools/bluetooth-logger.service.in | | | 2 | +- |
7 files changed, 24 insertions(+), 6 deletions(-)