[FFmpeg-cvslog] r21659 - trunk/configure

[Ramiro Polla]

On Wed, Feb 10, 2010 at 1:06 PM, Carl Eugen Hoyos <cehoyos at ag.or.at> wrote:
> Ramiro Polla <ramiro.polla <at> gmail.com> writes:
>> Carl prefers gsm/gsm.h, I prefer just gsm.h. The later can be fixed in
>> configure with --extra-(c|ld)flags, the former can't.
>
> So is there a distribution where only /usr/include/gsm.h is installed?

The thing is why did the distributions and programs start using
include/gsm/gsm.h in the first place? It doesn't seem necessary to me.
Also you could previously do --extra-cflags=-I../gsm-build-dir/inc
--extra-ldflags=-L../gsm-build-dir/<whatever>. That's not possible if
we use gsm/.

I went through the packages from "apt-cache rdepends libgsm1" and this
is how they're used:
checks both gsm.h and gsm/gsm.h in configure
asterisk
gst-plugins-bad

uses through FFmpeg (or at least it seems it does)
blender
ffmpeg2theora
gnusound
libsox-fmt-gsm
isdexport
libinstrudeo0

#include <gsm.h>
ekg
iaxclient
libopenh323-1.19.1
rplay-server
twinkle
yate

#include <gsm/gsm.h>
gpe-soundbite
libmediastreamer0

I prefer include/gsm.h, but what I prefer even more is consistency and
getting this "fixed", so either way is fine to me.

Mans, Diego, any other opinion?