On Thu, 22 Feb 2024 at 13:10, Joakim Tjernlund <Joakim.Tjernlund@xxxxxxxxxxxx> wrote: > > On Thu, 2024-02-22 at 12:54 +0000, Emil Velikov wrote: > > On Wed, 21 Feb 2024 at 11:19, Joakim Tjernlund > > <joakim.tjernlund@xxxxxxxxxxxx> wrote: > > > > > > From: Joakim Tjernlund <Joakim.Tjernlund@xxxxxxxxxxxx> > > > > > > Signed-off-by: Joakim Tjernlund <Joakim.Tjernlund@xxxxxxxxxxxx> > > > --- > > > lib/bluez.pc.in | 1 + > > > 1 file changed, 1 insertion(+) > > > > > > diff --git a/lib/bluez.pc.in b/lib/bluez.pc.in > > > index 3d6e59616..1c2f30b33 100644 > > > --- a/lib/bluez.pc.in > > > +++ b/lib/bluez.pc.in > > > @@ -1,6 +1,7 @@ > > > prefix=@prefix@ > > > exec_prefix=@exec_prefix@ > > > libdir=@libdir@ > > > +libexecdir=@libexecdir@ > > > includedir=@includedir@ > > > > > > > It seems to be unused in the pkg-config file. Why do we need this? > > > > > > Bluez does not but pkg-config is for other apps so if some app needs to know > something about bluez stuff living in libexecdir it can find out where that is. > "_some_ app needs to know _something_" sounds like the key here (emphasis mine). Do you have an example? Is the (bluetoothd/obexd) daemon location of interest, the cups backend, other? Thanks Emil
