On Tuesday 07 February 2012, Ruediger Meier wrote: > From: Ruediger Meier <ruediger.meier at ga-group.nl> > > This got broken in 26ea2a25. > If we configure --prefix=/tmp/bla then /tmp/bla/bin/sane-config > should tell us the right things instead of using any default search > paths. --- > tools/sane-config.in | 4 ++++ > 1 files changed, 4 insertions(+), 0 deletions(-) > > diff --git a/tools/sane-config.in b/tools/sane-config.in > index 1fae2e5..8e4b52a 100644 > --- a/tools/sane-config.in > +++ b/tools/sane-config.in > @@ -10,6 +10,10 @@ scriptname="sane-config" > prefix="@prefix@" > exec_prefix="@exec_prefix@" > > +# using our installed *.pc only - neither default nor user paths > +export PKG_CONFIG_LIBDIR="@libdir@/pkgconfig" > +export PKG_CONFIG_PATH="" > +
It's debatable wheather sane-config should find any other sane-backends.pc than the cleanly make installed one. If this would be wanted we could do only export PKG_CONFIG_PATH="@libdir@/pkgconfig" without touching PKG_CONFIG_LIBDIR. But IMO that use case is already covered by directly using pkg-config. The way I did it here we can be more sure to include/link against that sane-backends the called sane-config belongs to. Also it's IMO worth to think about declaring sane-config deprecated to remove it completely in some years. cu, Rudi > pkgconfig_package=sane-backends > > usage () > -- > 1.7.6.1
