Re: [Rivendell] Re: [Audacity-devel] Problem with libsoundtouch

[Richard Ash <richard@audacityteam.org>]

On Tue, 2008-04-08 at 12:44 -0400, Federico Grau wrote:
> Thanks for the response.  Agreed as per the "start hacking stuff" mess.  I am
> still becoming familiar with pkg-config, but it seems that the libsoundtouch
> version 1.3.1 creates "soundtouch-1.0.pc", not "soundtouch.pc" .  A quick test
> shows that the current audacity test still will not pick it up.

>     debiansid:~# cp /usr/lib/pkgconfig/libSoundTouch.pc /usr/lib/pkgconfig/soundtouch-1.0.pc
>     debiansid:~# pkg-config --exists --print-errors soundtouch
>     Package soundtouch was not found in the pkg-config search path.
>     Perhaps you should add the directory containing `soundtouch.pc'
>     to the PKG_CONFIG_PATH environment variable
>     No package 'soundtouch' found
>     debiansid:~# pkg-config --exists --print-errors soundtouch-1.0
>     debiansid:~# echo $?
>     0
Pardon? Audacity's acinclude.m4 file currently reads
PKG_CHECK_MODULES(SOUNDTOUCH, soundtouch-1.0 >= 1.3.1

you can argue that the version required needs changing, but it's
definitely checking for a soundtouch-1.0.pc file

> Before I go asking folks to switch to a different pkg-config name, what should
> the final target be (if simply "soundtouch", then I should contact the
> soundtouch developer and ask him to change things upstream)?
In general the package name. Versioning is only useful if it is likely
that multiple versions of the library will be installed at the same
time, so I wouldn't usually bother. It's not critical enough to try and
persuade upstream to change though (I would expect it to stay at "1.0"
until major API breakage requiring a re-write of clients occurred).

> Is the gentoo package of soundtouch patched to change its pkg-config file?
No - several other patches, but for build process and CFLAGS not the pc
file.

Richard