Wireshark-dev: Re: [Wireshark-dev] When to include RTP player?

From: Joerg Mayer <jmayer@xxxxxxxxx>
Date: Sun, 8 Oct 2006 20:06:39 +0200
On Sun, Oct 08, 2006 at 10:20:01AM +0200, Jaap Keuter wrote:
> Running configure without options, with portaudio-dev installed should
> build Wireshark with RTP player functionality. At least that is what this
> line in configure is saying:
>   --with-portaudio[=DIR]  use libportaudio (located in directory DIR, if supplied) for the rtp_player.  [default=yes, if available]
> But still it results in:
>                    Build rtp_player : no
> This is due to the fact that want_portaudio=ifavailable is set by default,
> and then this test evaluates to "no":
> if test "x$want_portaudio" = "xyes" ; then
>         portaudio_message="yes"
> else
>         portaudio_message="no"
> fi
> 
> My claim is that this last test be inverted, like so:
> if test "x$want_portaudio" = "xno" ; then
>         portaudio_message="no"
> else
>         portaudio_message="yes"
> fi
> 
> Am I right?

I don't think so: a) it works on my system as planned and b) the message
tells whether things were found, not what was requested. Have a look at
the configure output to see what is going on, for me, it looks like this
(without giving a portaudio argument to configure):

checking whether to use liblua for the lua scripting plugin... no
checking whether to use libportaudio for the rtp_player... yes
checking portaudio.h usability... yes
checking portaudio.h presence... yes
checking for portaudio.h... yes
checking for PortAudioStream... no
checking for Pa_Initialize in -lportaudio... yes
checking whether to enable ipv6 name resolution if available... yes

 ciao
     Joerg
-- 
Joerg Mayer                                           <jmayer@xxxxxxxxx>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.