iaxclient-devel — Development Discussion List

[Iaxclient-devel] Re: Aha: The next IAX2 bug (PPC only, I guess)..

[Mark S. <mar...@di...>]

No, it was nasty to start with and this just makes it even nastier.  I
think the cleaner way would be to do something like this:

struct sillystruct {
	struct iax2_frame fr2;
	unsigned char buffer[4096];
} tmp;

and then reference tmp.fr2 and tmp.buffer;

Mark

On 12 Jun 2003, Steve Kann wrote:

>
> Mark,
>
>     Here's a good one, that took a bit to figure out also.  This problem
> only occurs with MacOSX, although it just depends on which way the stack
> grows..
>
> in iax_send, you have the following code:
>         unsigned char buffer[4096];             /* Buffer -- must
> preceed fr2 */
>         struct iax_frame fr2;
>         struct iax_frame *fr;
>
> and later, you do this:
>         if (now) {
>                 fr = &fr2;
>         } else
>                 fr = iax_frame_new(DIRECTION_OUTGRESS, f->datalen);
>         if (!fr) {
>                 IAXERROR "Out of memory\n");
>                 return -1;
>         }
>
>         fprintf(stderr, "now=%d, fr=%x, &fr2=%x\n", now, fr, &fr2);
>         fprintf(stderr, "f->datalen=%d\n", f->datalen);
>
>         /* Copy our prospective frame into our immediate or
> retransmitted wrapper */
>         iax_frame_wrap(fr, f);
>
>         fprintf(stderr, "now=%d, fr=%x, &fr2=%x\n", now, fr, &fr2);
>
>
> (fprintfs are mine) which if (now=1) and f has data, copies some items
> from f into fr2, and then copies data to from f to fr.  This data ends
> up past the end of fr2, which you account for, on machines with one
> stack direction, with the buffer on the stack.
>
> So, I think it would be better to just do this instead:
>         double buffer[1024];             /* Buffer -- does double
> guarantee us proper alignment? */
>         struct iax_frame *fr;
>
> [...]
>
>        if (now) {
>                 fr = (struct iax_frame *)&buffer;
>         } else
>                 fr = iax_frame_new(DIRECTION_OUTGRESS, f->datalen);
>         if (!fr) {
>                 IAXERROR "Out of memory\n");
>                 return -1;
>         }
>
>         fprintf(stderr, "now=%d, fr=%x\n", now, fr);
>         fprintf(stderr, "f->datalen=%d\n", f->datalen);
>
>         /* Copy our prospective frame into our immediate or
> retransmitted wrapper */
>         iax_frame_wrap(fr, f);
>
>         fprintf(stderr, "now=%d, fr=%x\n", now, fr);
>
>
> Does this seem like it will be more portable?
>
> It works for me on MacOSX/PPC, Linux/x86, Win2K/x86.
>
> Attached also please find my current diff between my local libiax2 and
> digium's CVS.  It is still mostly portability fixes, plus the two
> bugfixes (this one, and the buf[len-1] = 0 issue).
>
> Next on the list: using IAX2, for some reason the DNID isn't being
> honored.  This is kinda strange, because using "iax2 debug" on the
> console of a * server, it shows the DNID properly, but I still end up in
> the "s" extension for the context, instead of the requested extension..
>
>
> -SteveK
>
>
>
>
> --
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."
>

RE: [Iaxclient-devel] iaxclient's first contributor

[Uriel C. <ur...@ad...>]

Can we learn more as to what these new changes entail?
What I make out of it is a Microsoft-Visual-C++ version, am I correct?
Uriel
  -----Original Message-----
  From: iax...@li... =
[mailto:iax...@li...]On Behalf Of Steve =
Kann
  Sent: Friday, June 13, 2003 7:46 PM
  To: iaxclient devel
  Subject: [Iaxclient-devel] iaxclient's first contributor



  This is just a note to thank Tili for becoming iaxclient's first =
contributor.

  Today, I just committed his contributions, which include some =
portability changes, as well as MSVC project files for the library, and =
a new simple Win32-only client, WinIAX.

  These are all available now in CVS.  (or should be real soon, =
sourceforge anonymous CVS seems to be lagging a bit -- I think it's =
running on a backup from last night, although the developer CVS access =
is working).

  -SteveK


--=20
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed =
Linux."
      =20

[Iaxclient-devel] iaxclient's first contributor

[Steve K. <st...@st...>]

This is just a note to thank Tili for becoming iaxclient's first
contributor.

Today, I just committed his contributions, which include some
portability changes, as well as MSVC project files for the library, and
a new simple Win32-only client, WinIAX.

These are all available now in CVS.  (or should be real soon,
sourceforge anonymous CVS seems to be lagging a bit -- I think it's
running on a backup from last night, although the developer CVS access
is working).

-SteveK


-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

Re: [Iaxclient-devel] Compiling with MinGW/Cygwin and Win32 Latency

[Darren S. <da...@ba...>]

Hi all

I found when i installed wxwindows, i had to use --enable-debug as well =
on the commandline as well as the --disable-shared i think it was, to =
force it to create a static library.

It'll then create a debug .a file in the wxwindows/lib dir =
libwxs<something>d-4.2.0.a , can't remember the exact filename (i'm 120 =
miles from my pc at home atm) anyway, i had to rename it to remove the =
-4.2.0 bit for it to work.

Also, when you set the WXWIN variable, use =
/c:/<windows-path-to-wxwindows-dir> instead of the cygwin path, as mingw =
wont be able to find it.

PS. Great work on the winiax client Faizan, looks nice in the quick test =
i gave it from my laptop :-)

Best Regards

Darren ']data[' Smith
Game Digital Ltd

  ----- Original Message -----=20
  From: Steve Kann=20
  To: ur...@ad...=20
  Cc: 'iaxclient devel'=20
  Sent: Friday, June 13, 2003 3:04 PM
  Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin and Win32 =
Latency


  On Thu, 2003-06-12 at 23:12, Uriel Carrasquilla wrote:=20
    Steve:
    Right on!  My next step is to install wxwindows from =
www.wxwindows.org as per your instructions with MinGW.  I think I am =
going to call it a day but either tomorrow or Saturday I will get to it.
    I am also going to play with the settings in portaudio and will let =
the list know what worked for me.  I will document the steps to get =
everything up and running on a Windows XP environment so we can put it =
in a README-WIN.txt file.
    Thank you for your invaluable support, without you I would have not =
made it this far.=20


  Great!  I'm glad I could help, and I'm glad you stuck it out.

  While I think it's a bit harder to get set up with MinGW and =
wxwindows, that it would be to use VC (once Faizan's project files are =
in place, etc), I think it's better, because then changes and =
contributions you make are helpful for people on platforms other than =
Windows.

  Bill still doesn't have 100% of the market yet!

  -SteveK




    Regards,
    Uriel=20
      -----Original Message-----
      From: Steve Kann [mailto:st...@st...]
      Sent: Thursday, June 12, 2003 9:37 AM
      To: ur...@ad...
      Cc: 'iaxclient devel'
      Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin and =
Win32 Latency


      On Wed, 2003-06-11 at 22:41, Uriel Carrasquilla wrote:=20
        Steve:
        It is now working with the "make" from Cygwin.  I had to =
download it from http://cygwin.com/setup.exe as it is not part of the =
default install.
        I was able to compile with "make clena" followed by "make" under =
iaxclient/simpleclient/testcall.  It works and I tested it and modified =
it to use my own *.  There was quite a bit of noise and quite a bit of =
delay but it is very promissing.=20

      Cool.  I'm glad you got it working.  I guess I installed cygwin a =
long time ago, and I probably did install more than the default install, =
so we should note this in the README with the sources.

      Thanks for sticking in there!

      The latency can be adjusted somewhat by setting an environment =
variable, PA_MIN_LATENCY_MSEC  It defaults to 200ms for Win9x, and 400ms =
for NT.  Try setting it to something smaller, and it might work for you. =
 Some people have tried setting this to 50ms or so, with success, but it =
depends on your system.

      The portaudio people set this by default pretty high on windows, =
because windows has pretty bad real-time support.  It's better, by =
default, on Linux/MacOSX.

      All of this is really in the portaudio library code, so if you're =
looking to change things or research them, look in the portaudio =
directory, and/or the portaudio website and mailing lists -- there's =
lots of info on it there, and I think they're improving things for their =
next release.



        Then I got ambitious and tried the same steps undex =
iaxclient/simpleclient/wx.  I watched in horror the screen go for quite =
a while.  Then it stopped with a message "1 error in wx.o".  I tried to =
redirect the output to file so I could attach it here but only got the =
first few lines of the "Makefile" execution.  Then, when the Cygwin make =
takes over, it all went back to the STD output, my screen.
        Since I made it this far, I am now more committed than ever.
        Did I miss a step to compile the "GUI" version?=20

      And if you thought getting the environment setup for compiling =
"testcall" was complicated, wait till you try compiling with wxwindows =
:)  (OK, it's not _too_ bad, really.  Several people besides me have =
done this already).

      Basically, what you need to do is get wxwindows from =
wxwindows.org, compile that with mingw (when you do this, make sure you =
compile it to make _static libraries_, not DLLs), and then if you have =
the WXWIN environment variable set properly, the build of wx will =
succeed.

      The errors you got are all probably because you don't have wxwin =
installed/compiled, so it can't find the wxwin headers, and then the =
compiler can't make sense out of the rest of the code.

      -SteveK



        Regards,
        Uriel=20
--=20
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed =
Linux."=20

RE: [Iaxclient-devel] Compiling with MinGW/Cygwin and Win32 Latency

[Steve K. <st...@st...>]

On Thu, 2003-06-12 at 23:12, Uriel Carrasquilla wrote:

> Steve:
> Right on!  My next step is to install wxwindows from
> www.wxwindows.org as per your instructions with MinGW.  I think I am
> going to call it a day but either tomorrow or Saturday I will get to
> it.
> I am also going to play with the settings in portaudio and will let
> the list know what worked for me.  I will document the steps to get
> everything up and running on a Windows XP environment so we can put it
> in a README-WIN.txt file.
> Thank you for your invaluable support, without you I would have not
> made it this far.



Great!  I'm glad I could help, and I'm glad you stuck it out.

While I think it's a bit harder to get set up with MinGW and wxwindows,
that it would be to use VC (once Faizan's project files are in place,
etc), I think it's better, because then changes and contributions you
make are helpful for people on platforms other than Windows.

Bill still doesn't have 100% of the market yet!

-SteveK



>  
> Regards,
> Uriel
> 
>         -----Original Message-----
>         From: Steve Kann [mailto:st...@st...]
>         Sent: Thursday, June 12, 2003 9:37 AM
>         To: ur...@ad...
>         Cc: 'iaxclient devel'
>         Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin and
>         Win32 Latency
>         
>         
>         On Wed, 2003-06-11 at 22:41, Uriel Carrasquilla wrote: 
>         
>         > Steve:
>         > It is now working with the "make" from Cygwin.  I had to
>         > download it from http://cygwin.com/setup.exe as it is not
>         > part of the default install.
>         > I was able to compile with "make clena" followed by "make"
>         > under iaxclient/simpleclient/testcall.  It works and I
>         > tested it and modified it to use my own *.  There was quite
>         > a bit of noise and quite a bit of delay but it is very
>         > promissing.
>         
>         
>         Cool.  I'm glad you got it working.  I guess I installed
>         cygwin a long time ago, and I probably did install more than
>         the default install, so we should note this in the README with
>         the sources.
>         
>         Thanks for sticking in there!
>         
>         The latency can be adjusted somewhat by setting an environment
>         variable, PA_MIN_LATENCY_MSEC  It defaults to 200ms for Win9x,
>         and 400ms for NT.  Try setting it to something smaller, and it
>         might work for you.  Some people have tried setting this to
>         50ms or so, with success, but it depends on your system.
>         
>         The portaudio people set this by default pretty high on
>         windows, because windows has pretty bad real-time support. 
>         It's better, by default, on Linux/MacOSX.
>         
>         All of this is really in the portaudio library code, so if
>         you're looking to change things or research them, look in the
>         portaudio directory, and/or the portaudio website and mailing
>         lists -- there's lots of info on it there, and I think they're
>         improving things for their next release.
>         
>         
>         
>         > Then I got ambitious and tried the same steps undex
>         > iaxclient/simpleclient/wx.  I watched in horror the screen
>         > go for quite a while.  Then it stopped with a message "1
>         > error in wx.o".  I tried to redirect the output to file so I
>         > could attach it here but only got the first few lines of the
>         > "Makefile" execution.  Then, when the Cygwin make takes
>         > over, it all went back to the STD output, my screen.
>         > Since I made it this far, I am now more committed than ever.
>         > Did I miss a step to compile the "GUI" version?
>         
>         
>         And if you thought getting the environment setup for compiling
>         "testcall" was complicated, wait till you try compiling with
>         wxwindows :)  (OK, it's not _too_ bad, really.  Several people
>         besides me have done this already).
>         
>         Basically, what you need to do is get wxwindows from
>         wxwindows.org, compile that with mingw (when you do this, make
>         sure you compile it to make _static libraries_, not DLLs), and
>         then if you have the WXWIN environment variable set properly,
>         the build of wx will succeed.
>         
>         The errors you got are all probably because you don't have
>         wxwin installed/compiled, so it can't find the wxwin headers,
>         and then the compiler can't make sense out of the rest of the
>         code.
>         
>         -SteveK
>         
>         
>         
>         > Regards,
>         > Uriel

-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

Re: [Iaxclient-devel] Winiax binary

[Steve K. <st...@st...>]

Very cool, Faizan!


Here's what I see about this, which I imagine is just a starting point
for you.

1) Good:  It's a bunch smaller than the WxWindows app.  136kb vs 1.4MB.
2) Bad: Any enhancements you make here will be Win32 only.

But, it is great that you've been able to use the library with VC, and
etc, which might help people making Win32-only clients.  

I'll look at your patches and etc today, and see about applying them.

Thanks for contributing!

-SteveK



On Thu, 2003-06-12 at 23:11, Faizan Tili wrote:

> Here is the release binary file for WinIAX Client.

http://www.tilizone.com/WinIAX_bin.zip
-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

[Iaxclient-devel] Winiax binary

[Faizan T. <fa...@ti...>]

Here is the release binary file for WinIAX Client.
http://www.tilizone.com/WinIAX_bin.zip

[Iaxclient-devel] IAX client built in VC.

[Faizan T. <fa...@ti...>]

Hi.

I built a simple IAX Client in VC. I had to configure some options to =
compile libiax and other libs. I also created sox lib for VC. The =
patches are mostly project files.
Download the vc_patches.zip and overwrite the files in your iaxclient =
directory from this zip file. http://www.tilizone.com/vc_patches.zip
The only changes to actual code are in sox.h and iaxcilent_lib.c where I =
added the preprocessers like this for vc.=20
#elif _MSC_VER
#include <stdarg.h>

and in sox .h like this
#elif _MSC_VER
#include <stdarg.h>
#include <process.h>

vararg.h seems to confuse vc.=20

gsmlib compiled didnt work with for me. Iaxcilent_lib doesnt compile =
with it. gets error of corrupt file.


It compiles fine. Also the project changes were about include paths and =
mutithreaded support, else it wont compile with your multithreaded =
project.

A vc client for IAX is at http://www.tilizone.com/WinIAX.zip. Extract it =
to simpleclient directory just beside wx, testcall=20
directories.
The compilation sequence would be
gsm
sox
iaxclient_lib
WinIAX

Mail me if someone gets a problem with it.
Stevek:
I will be updating this client constantly so I think including it in cvs =
might help developers working with VC.
Thank you.

[Iaxclient-devel] IAX client built in VC.

[Faizan T. <fa...@ti...>]

Hi.

I built a simple IAX Client in VC. I had to configure some options to =
compile libiax and other libs. I also created sox lib for VC. The =
patches are mostly project files.
Download the vc_patches.zip and overwrite the files in your iaxclient =
directory from this zip file. http://www.tilizone.com/vc_patches.zip
The only changes to actual code are in sox.h and iaxcilent_lib.c where I =
added the preprocessers like this for vc.=20
#elif _MSC_VER
#include <stdarg.h>

and in sox .h like this
#elif _MSC_VER
#include <stdarg.h>
#include <process.h>

vararg.h seems to confuse vc.=20

gsmlib compiled didnt work with for me. Iaxcilent_lib doesnt compile =
with it. gets error of corrupt file.


It compiles fine. Also the project changes were about include paths and =
mutithreaded support, else it wont compile with your multithreaded =
project.

A vc client for IAX is at http://www.tilizone.com/WinIAX.zip. Extract it =
to simpleclient directory just beside wx, testcall=20
directories.
The compilation sequence would be
gsm
sox
iaxclient_lib
WinIAX
Stevek:
I will be updating this client constantly so I think including it in cvs =
might help developers working with VC.
Thank you.

RE: [Iaxclient-devel] Compiling with MinGW/Cygwin and Win32 Latency

[Uriel C. <ur...@ad...>]

Steve:
Right on!  My next step is to install wxwindows from www.wxwindows.org =
as per your instructions with MinGW.  I think I am going to call it a =
day but either tomorrow or Saturday I will get to it.
I am also going to play with the settings in portaudio and will let the =
list know what worked for me.  I will document the steps to get =
everything up and running on a Windows XP environment so we can put it =
in a README-WIN.txt file.
Thank you for your invaluable support, without you I would have not made =
it this far.

Regards,
Uriel
  -----Original Message-----
  From: Steve Kann [mailto:st...@st...]
  Sent: Thursday, June 12, 2003 9:37 AM
  To: ur...@ad...
  Cc: 'iaxclient devel'
  Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin and Win32 =
Latency


  On Wed, 2003-06-11 at 22:41, Uriel Carrasquilla wrote:=20
    Steve:
    It is now working with the "make" from Cygwin.  I had to download it =
from http://cygwin.com/setup.exe as it is not part of the default =
install.
    I was able to compile with "make clena" followed by "make" under =
iaxclient/simpleclient/testcall.  It works and I tested it and modified =
it to use my own *.  There was quite a bit of noise and quite a bit of =
delay but it is very promissing.=20

  Cool.  I'm glad you got it working.  I guess I installed cygwin a long =
time ago, and I probably did install more than the default install, so =
we should note this in the README with the sources.

  Thanks for sticking in there!

  The latency can be adjusted somewhat by setting an environment =
variable, PA_MIN_LATENCY_MSEC  It defaults to 200ms for Win9x, and 400ms =
for NT.  Try setting it to something smaller, and it might work for you. =
 Some people have tried setting this to 50ms or so, with success, but it =
depends on your system.

  The portaudio people set this by default pretty high on windows, =
because windows has pretty bad real-time support.  It's better, by =
default, on Linux/MacOSX.

  All of this is really in the portaudio library code, so if you're =
looking to change things or research them, look in the portaudio =
directory, and/or the portaudio website and mailing lists -- there's =
lots of info on it there, and I think they're improving things for their =
next release.



    Then I got ambitious and tried the same steps undex =
iaxclient/simpleclient/wx.  I watched in horror the screen go for quite =
a while.  Then it stopped with a message "1 error in wx.o".  I tried to =
redirect the output to file so I could attach it here but only got the =
first few lines of the "Makefile" execution.  Then, when the Cygwin make =
takes over, it all went back to the STD output, my screen.
    Since I made it this far, I am now more committed than ever.
    Did I miss a step to compile the "GUI" version?=20

  And if you thought getting the environment setup for compiling =
"testcall" was complicated, wait till you try compiling with wxwindows =
:)  (OK, it's not _too_ bad, really.  Several people besides me have =
done this already).

  Basically, what you need to do is get wxwindows from wxwindows.org, =
compile that with mingw (when you do this, make sure you compile it to =
make _static libraries_, not DLLs), and then if you have the WXWIN =
environment variable set properly, the build of wx will succeed.

  The errors you got are all probably because you don't have wxwin =
installed/compiled, so it can't find the wxwin headers, and then the =
compiler can't make sense out of the rest of the code.

  -SteveK



    Regards,
    Uriel=20

[Iaxclient-devel] todays updates

[Steve K. <st...@st...>]

A few small things today:

1) IAX2 support getting much closer.  smashed a few bugs in libiax2, and
we're now working OK on all platforms.  Still some call-handling
"issues", esp when you hangup.

2) New callback handlers in wx: I think I finally figured out how to
lock without deadlock, so that callback-initiated updates (currently
just the level meters, and the status area), are done in a saner way
(i.e. immediately, instead of setting some variables, and having the
idle look check them).

3) command-line parameters.  You can now do things like "wx -h"
(linux/windows), or "wx.app/Contents/MacOS/wx -h" and get help, and then
do "wx -d <destination>" to make an immediate call to someplace.




-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

[Iaxclient-devel] Aha: The next IAX2 bug (PPC only, I guess)..

[Steve K. <st...@st...>]

Mark,

    Here's a good one, that took a bit to figure out also.  This problem
only occurs with MacOSX, although it just depends on which way the stack
grows..

in iax_send, you have the following code:
        unsigned char buffer[4096];             /* Buffer -- must
preceed fr2 */
        struct iax_frame fr2;
        struct iax_frame *fr;

and later, you do this:
        if (now) {
                fr = &fr2;
        } else
                fr = iax_frame_new(DIRECTION_OUTGRESS, f->datalen);
        if (!fr) {
                IAXERROR "Out of memory\n");
                return -1;
        }

        fprintf(stderr, "now=%d, fr=%x, &fr2=%x\n", now, fr, &fr2);
        fprintf(stderr, "f->datalen=%d\n", f->datalen);

        /* Copy our prospective frame into our immediate or
retransmitted wrapper */
        iax_frame_wrap(fr, f);

        fprintf(stderr, "now=%d, fr=%x, &fr2=%x\n", now, fr, &fr2);


(fprintfs are mine) which if (now=1) and f has data, copies some items
from f into fr2, and then copies data to from f to fr.  This data ends
up past the end of fr2, which you account for, on machines with one
stack direction, with the buffer on the stack.

So, I think it would be better to just do this instead:
        double buffer[1024];             /* Buffer -- does double
guarantee us proper alignment? */
        struct iax_frame *fr;

[...]

       if (now) {
                fr = (struct iax_frame *)&buffer;
        } else
                fr = iax_frame_new(DIRECTION_OUTGRESS, f->datalen);
        if (!fr) {
                IAXERROR "Out of memory\n");
                return -1;
        }

        fprintf(stderr, "now=%d, fr=%x\n", now, fr);
        fprintf(stderr, "f->datalen=%d\n", f->datalen);

        /* Copy our prospective frame into our immediate or
retransmitted wrapper */
        iax_frame_wrap(fr, f);

        fprintf(stderr, "now=%d, fr=%x\n", now, fr);


Does this seem like it will be more portable?

It works for me on MacOSX/PPC, Linux/x86, Win2K/x86.

Attached also please find my current diff between my local libiax2 and
digium's CVS.  It is still mostly portability fixes, plus the two
bugfixes (this one, and the buf[len-1] = 0 issue).

Next on the list: using IAX2, for some reason the DNID isn't being
honored.  This is kinda strange, because using "iax2 debug" on the
console of a * server, it shows the DNID properly, but I still end up in
the "s" extension for the context, instead of the requested extension..


-SteveK




-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

RE: [Iaxclient-devel] Compiling with MinGW/Cygwin and Win32 Latency

[Steve K. <st...@st...>]

On Wed, 2003-06-11 at 22:41, Uriel Carrasquilla wrote:

> Steve:
> It is now working with the "make" from Cygwin.  I had to download it
> from http://cygwin.com/setup.exe as it is not part of the default
> install.
> I was able to compile with "make clena" followed by "make" under
> iaxclient/simpleclient/testcall.  It works and I tested it and
> modified it to use my own *.  There was quite a bit of noise and quite
> a bit of delay but it is very promissing.


Cool.  I'm glad you got it working.  I guess I installed cygwin a long
time ago, and I probably did install more than the default install, so
we should note this in the README with the sources.

Thanks for sticking in there!

The latency can be adjusted somewhat by setting an environment variable,
PA_MIN_LATENCY_MSEC  It defaults to 200ms for Win9x, and 400ms for NT. 
Try setting it to something smaller, and it might work for you.  Some
people have tried setting this to 50ms or so, with success, but it
depends on your system.

The portaudio people set this by default pretty high on windows, because
windows has pretty bad real-time support.  It's better, by default, on
Linux/MacOSX.

All of this is really in the portaudio library code, so if you're
looking to change things or research them, look in the portaudio
directory, and/or the portaudio website and mailing lists -- there's
lots of info on it there, and I think they're improving things for their
next release.



> Then I got ambitious and tried the same steps undex
> iaxclient/simpleclient/wx.  I watched in horror the screen go for
> quite a while.  Then it stopped with a message "1 error in wx.o".  I
> tried to redirect the output to file so I could attach it here but
> only got the first few lines of the "Makefile" execution.  Then, when
> the Cygwin make takes over, it all went back to the STD output, my
> screen.
> Since I made it this far, I am now more committed than ever.
> Did I miss a step to compile the "GUI" version?


And if you thought getting the environment setup for compiling
"testcall" was complicated, wait till you try compiling with wxwindows
:)  (OK, it's not _too_ bad, really.  Several people besides me have
done this already).

Basically, what you need to do is get wxwindows from wxwindows.org,
compile that with mingw (when you do this, make sure you compile it to
make _static libraries_, not DLLs), and then if you have the WXWIN
environment variable set properly, the build of wx will succeed.

The errors you got are all probably because you don't have wxwin
installed/compiled, so it can't find the wxwin headers, and then the
compiler can't make sense out of the rest of the code.

-SteveK



> Regards,
> Uriel
> 
>         -----Original Message-----
>         From: iax...@li...
>         [mailto:iax...@li...]On Behalf
>         Of Steve Kann
>         Sent: Wednesday, June 11, 2003 7:34 PM
>         To: ur...@ad...
>         Cc: iaxclient devel
>         Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin
>         
>         
>         On Wed, 2003-06-11 at 19:55, Uriel Carrasquilla wrote: 
>         
>         > Steve:
>         > My first step: went to ieaxclient/lib, typed: "make clean" 
>         > Results: +ve
>         > My second step: from iaxclient/lib typed: "make"
>         > Resulting message:
>         > failed make (e=2): the system cannot find the file specified
>         > c"\MinGW\bin\make.exe **** [gsm/src/add.o] Error 2
>         
>         
>         hmm, OK, this is interesting.  
>         
>         Your build environment is different from mine, in that you're
>         using a "make" provided by MinGW, as opposed to the cygwin
>         make.  Their make might be broken in some way, although I
>         think someone built sucessfully with MinGW with "msys"
>         installed.
>         
>         The way my environment is set up, I have cygwin installed, and
>         MinGW installed, and then I have the MinGW tools installed
>         ahead of the cygwin stuff in my path.  I.e. my path is:
>         
>         
>                 /cygdrive/c/MINGW/bin:/usr/local/bin:/usr/bin:/bin:/cygdrive/c/SPRY/BIN:/cygdriv
>                 e/c/WINDOWS:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS/system32/WBEM:/cygd
>                 rive/c/Program Files/Real/Helix Producer
>                 Basic:/cygdrive/c/Program Files/Microso
>                 ft Visual
>                 Studio/Common/Tools/WinNT:/cygdrive/c/Program
>                 Files/Microsoft Visual S
>                 tudio/Common/MSDev98/Bin:/cygdrive/c/Program
>                 Files/Microsoft Visual Studio/Commo
>                 n/Tools:/cygdrive/c/Program Files/Microsoft Visual
>                 Studio/VC98/bin 
>         
>         
>         (all that's really important is that the MinGW binaries come
>         before the cygwin binaries).
>         
>         Then, I run a shell from cygwin (using the icon the cygwin
>         install leaves on the desktop, which gives me a terminal
>         running bash), and do the make from there.
>         
>         But, my MINGW directory doesn't have "make.exe" in it. 
>         There's a mingw32-make.exe, but the purposely don't call it
>         "make.exe", because it sucks :)
>         
>         I can't understand the particular error your make gave you,
>         but I don't know what file it's talking about.  (I think the
>         note is that it's trying to make gsm/src/add.o, which is
>         should do from the implicit rule from gsm/src/add.c).
>         
>         
>         So, I think the easiest way to get you going is to get
>         yourself cygwin (just run http://cygwin.com/setup.exe), find
>         out what that make you're using is and get rid of it, then
>         build with cygwin's tools (except for the compiler, for that
>         use mingw).
>         
>         The rest of your research, below, is unlikely to get you
>         anywhere helpful.  I don't maintain any of the other Makefiles
>         other than lib/Makefile simpleclient/testcall/Makefile and
>         simpleclient/wx/Makefile.  Even if those other Makefiles work,
>         they'll give you some library which isn't going to help you.
>         
>         
>         Also, please post to the mailing list; other people are
>         working through the same thing (]data[ from IRC, for example,
>         just got a whole "wx.exe" build going himself), and the
>         discussion can either help others, or perhaps others can help
>         you.
>         
>         -SteveK
>         
>         
>         > Research:
>         > went to iaxclient/lib/gsm/src: there is no add.o, just add.c
>         > There is a "makefile" here, so I typed "make clean";
>         > results: +ve
>         >  
>         > Hacking: from iaxclient/lib/gsm, typed "make".  Results: +ve
>         > Went back to iaxclient/lib typed: "make"
>         > Resulting message:
>         > The same but with code.o missing instead of add.o
>         >  
>         > I will greatly appreciate your guidance through these
>         > difficulties.
>         >  
>         >  
>         > Regards,
>         > Uriel
>         > 
>         >         -----Original Message-----
>         >         From: iax...@li...
>         >         [mailto:iax...@li...]On Behalf Of Steve Kann
>         >         Sent: Wednesday, June 11, 2003 10:21 AM
>         >         To: ur...@ad...
>         >         Cc: iaxclient devel
>         >         Subject: RE: [Iaxclient-devel] Compiling with
>         >         MinGW/Cygwin
>         >         
>         >         
>         >         Uriel,
>         >         
>         >             There's three "maintained" makefiles within the
>         >         project.  The Makefile in iaxclient/lib, and the
>         >         Makefiles in simpleclient/testcall and
>         >         simpleclient/wx.
>         >         
>         >         Both of the simpleclient/*/Makefiles will call the
>         >         Makefile in lib to make the library, as both clients
>         >         use the library, and thus require the library
>         >         (libiaxclient.a) to be built.
>         >         
>         >         So, from clean CVS, you should be able to just go to
>         >         simpleclient/testcall, and type "make".
>         >         
>         >         However, if you've tried other things, I'd say you'd
>         >         be best off going to iaxclient/lib, typing "make
>         >         clean", then "make".  Then, go to the client you
>         >         want to make and type "make clean", "make".
>         >         
>         >         (the client Makefiles won't "clean" the library).
>         >         
>         >         First, try making "testcall", since for "wx", you'll
>         >         also need to have wxwindows installed, etc. 
>         >         Definately a better first step is to compile
>         >         testcall.
>         >         
>         >         And yes, there's no install targets in the
>         >         Makefiles.  You don't need to install the library,
>         >         and the executable targets are standalone (i.e. for
>         >         wx, there's "wx.exe" for windows, "wx" for linux,
>         >         and "wx.app" for MacOSX).
>         >         
>         >         
>         >         
>         >         On Wed, 2003-06-11 at 00:00, Uriel Carrasquilla
>         >         wrote:  
>         >         
>         >         > Steve:
>         >         > I am having a hard time compiling with MinGW and
>         >         > Gygwin.
>         >         > I downloaded the CVS from Monday night.
>         >         > I went to the /iaxclient/simpleclient/wx  (where
>         >         > there is a Makefile) and typed: make
>         >         > Problems developed in the lib/gsm.  I can see in
>         >         > the wx/Makefile that we are trying to make
>         >         > iaxclient.a from lib/gsm.  So I went over and type
>         >         > make iaxclient.a
>         >         > could not find a file.  So I went to the gsm
>         >         > subdirectory and somewhere in there there was
>         >         > another makefile (lower case which is normally a
>         >         > second choice for make).  I did a make.
>         >         > Went back one leve to lib/gsm and executed make 
>         >         > Got another file missing.  
>         >         >  
>         >         > My question: is there a sequence of "make" that I
>         >         > have to execute?
>         >         > what would it be?
>         >         > I could not see and "install" in any of the
>         >         > Makefile.  is it by design?
>         >         > Regards,
>         >         > Uriel 
>         >         > 
>         >         >         -----Original Message-----
>         >         >         From:
>         >         >         iax...@li... [mailto:iax...@li...]On Behalf Of Steve Kann
>         >         >         Sent: Tuesday, June 10, 2003 7:48 PM
>         >         >         To: iaxclient devel
>         >         >         Subject: [Iaxclient-devel] some updates,
>         >         >         and Ideas for contributions..
>         >         >         
>         >         >         
>         >         >         1) (most relevant): put iax call
>         >         >         processing (including audio) into a
>         >         >         separate thread.  This helps the most when
>         >         >         you do things that block the GUI thread,
>         >         >         like resizing the window (Win32 only?). 
>         >         >         And it seems to also help the Mac a bit(*)
>         >         >         
>         >         >         (*) The volume meters, implemented with
>         >         >         progress bars via wxwindows on the mac,
>         >         >         eat a lot of CPU for their animation.  Not
>         >         >         that it doesn't look good.  I think that
>         >         >         this caused some skips on the Mac.
>         >         >         
>         >         >         2) Fixed the DTMF buttons that I broke
>         >         >         sometime today or last night.
>         >         >         
>         >         >         3) Fixed PTT a bit.  (looking for feedback
>         >         >         on how this works).
>         >         >         
>         >         >         Also, due to a byproduct of the way I did
>         >         >         things, if you enable then disable PTT,
>         >         >         you'll also be enabling silence
>         >         >         detection/suppression.  This will make the
>         >         >         client not spit out any audio frames until
>         >         >         the input audio level reaches -40 DB.  
>         >         >         
>         >         >         There's been a lot of interest here on the
>         >         >         list and on IRC from a growing community. 
>         >         >         That's cool.  People asked what they can
>         >         >         help with, so here's some ideas for
>         >         >         adventurous souls:
>         >         >         
>         >         >         
>         >         >         1) IAX2:  You can build it via my
>         >         >         Makefiles by setting IAXVER=2 at the top
>         >         >         of the  
>         >         >                        library Makefile, or
>         >         >         building the library by running "make
>         >         >         IAXVER=2".  It 
>         >         >                        doesn't work quite right,
>         >         >         though, so if someone could try and figure
>         >         >         that one 
>         >         >                        out, it would be good. 
>         >         >         Once it's working, IAX2 should offer us a
>         >         >         bunch of 
>         >         >                        quality improvements,
>         >         >         especially over the internet.
>         >         >         
>         >         >         2) Registration:  People out there want
>         >         >         this, and it will make the apps/library
>         >         >         more     
>         >         >                        useful to the community. 
>         >         >         Shouldn't be too hard, but will need to be
>         >         >         a bit     
>         >         >                        careful about keeping track
>         >         >         of calls, sessions, peers, etc.
>         >         >         
>         >         >         3) A maintainer for VC++ Makefiles and/or
>         >         >         .dsw files.  I don't know this stuff, and
>         >         >         I 
>         >         >                       don't like tools you need
>         >         >         your mouse for.  But, if it helps people
>         >         >         get more 
>         >         >                       involved, I'm all for
>         >         >         keeping a current .dsw/dsp or whatever
>         >         >         file in CVS, one 
>         >         >                       for each of the Makefiles, I
>         >         >         guess (lib, testcall, wx).
>         >         >         
>         >         >         4) Exposing Audio Settings:  Make controls
>         >         >         (library functions and GUI) for
>         >         >         enumerating and choosing audio
>         >         >         input/output devices.  This may require
>         >         >         either moving to the standard portaudio
>         >         >         callback interface, or hacking pablio to
>         >         >         allow you to choose particular devices. 
>         >         >         Also, expose setting the input and output
>         >         >         "levels".  It's probably best to allow
>         >         >         them to change this while the app is
>         >         >         running, so you'll need to close/re-open
>         >         >         the audio device, etc.
>         >         >         
>         >         >         5) MacOSX Mono audio problem:  Currently
>         >         >         MacOSX audio comes only out of the left
>         >         >         channel.  Seems like a portaudio problem
>         >         >         to track down.
>         >         >         
>         >         >         6) silence detection / dynamic range
>         >         >         compression:  Figure out good values or
>         >         >         algorithms to make the client
>         >         >         automatically (a) not send any packets
>         >         >         when there's no speech, (b) put out good
>         >         >         consistent volume when there is speech,
>         >         >         even if people don't have consistent
>         >         >         microphone/soundcard settings, use laptop
>         >         >         microphones or nice headsets.
>         >         >         
>         >         >         7) Additional codec support:  I'd start
>         >         >         with uLaw, to make some #iaxclient user
>         >         >         happy, but also because it's pretty easy
>         >         >         to implement, then also try iLBC and/or
>         >         >         Speex.  Probably want one way for the user
>         >         >         to choose their preferred codec.
>         >         >         
>         >         >         Hmm, that's a bunch of stuff :)
>         >         >         
>         >         >         If anyone wants to step up for this stuff,
>         >         >         let the list know, so we all don't
>         >         >         duplicate each other's work.
>         >         >         
>         >         >         
>         >         >         Happy IAX clienting!
>         >         >         
>         >         >         -SteveK
>         >         >         
>         >         >         
>         >         >         
>         >         >         
>         >         >         
>         >         >         -- 
>         >         >           Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
>         >         >                         HorizonLive.com - collaborate . interact . learn
>         >         >            "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."
>         >         
>         >         -- 
>         >           Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
>         >                         HorizonLive.com - collaborate . interact . learn
>         >            "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."
>         
>         -- 
>           Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
>                         HorizonLive.com - collaborate . interact . learn
>            "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

RE: [Iaxclient-devel] RE: Compiling with MinGW/Cygwin (an Illogical Solution)

[Uriel C. <ur...@ad...>]

Syed:
I followed your instructions with one change:
sh script.sh
when I tried to execute "sh script.h" I got a message that the file did not
exist.

However, I got an error messge
error 2: Syntax error: EOF is in backquote subs

What I do find curious and you must be up to something is that the
iaxclient/wx/ make is giving me errors around the EOF issue.

Regards,
Uriel

-----Original Message-----
From: iax...@li...
[mailto:iax...@li...]On Behalf Of SYED
OBAID AMIN
Sent: Thursday, June 12, 2003 6:17 AM
To: iax...@li...
Subject: [Iaxclient-devel] RE: Compiling with MinGW/Cygwin (an Illogical
Solution)


Hi

Just read the prob lem of Uriel this sort of problem was also happening with
me and i found very illogical thing .

i have the same configuration as discussed by steve and the have same
problem as discussed by Uriel :)


so start cygwin , goto /iaxclient/lib and type
mingw32-make -n >script.sh
sh script.h

i dunno why this is happening but it works for me hopefully for others .

Bye




>From: iax...@li...
>Reply-To: iax...@li...
>To: iax...@li...
>Subject: Iaxclient-devel digest, Vol 1 #19 - 2 msgs
>Date: Wed, 11 Jun 2003 19:04:08 -0700
>MIME-Version: 1.0
>Received: from sc8-sf-list2.sourceforge.net ([66.35.250.206]) by
>mc7-f3.law1.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Wed, 11 Jun
>2003 19:05:05 -0700
>Received: from sc8-sf-list1-b.sourceforge.net ([10.3.1.13]
>helo=sc8-sf-list1.sourceforge.net)by sc8-sf-list2.sourceforge.net with
>esmtp (Exim 3.31-VA-mm2 #1 (Debian))id 19QHSw-0008QL-00; Wed, 11 Jun 2003
>19:05:26 -0700
>X-Message-Info: JGTYoYF78jEHjJx36Oi8+Q1OJDRSDidP
>X-Mailer: Mailman v2.0.9-sf.net
>Sender: iax...@li...
>Errors-To: iax...@li...
>X-BeenThere: iax...@li...
>X-Mailman-Version: 2.0.9-sf.net
>Precedence: bulk
>List-Help:
><mailto:iax...@li...?subject=help>
>List-Post: <mailto:iax...@li...>
>List-Subscribe:
><https://lists.sourceforge.net/lists/listinfo/iaxclient-devel>,<mailto:iaxc
lie...@li...?subject=subscribe>
>List-Id: Discussion of development of Cross-platform IAX clients
><iaxclient-devel.lists.sourceforge.net>
>List-Unsubscribe:
><https://lists.sourceforge.net/lists/listinfo/iaxclient-devel>,<mailto:iaxc
lie...@li...?subject=unsubscribe>
>List-Archive:
><http://sourceforge.net/mailarchive/forum.php?forum=iaxclient-devel>
>Message-Id: <E19...@sc...>
>Return-Path: iax...@li...
>X-OriginalArrivalTime: 12 Jun 2003 02:05:05.0460 (UTC)
>FILETIME=[0AB10F40:01C33087]
>
>Send Iaxclient-devel mailing list submissions to
>	iax...@li...
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	https://lists.sourceforge.net/lists/listinfo/iaxclient-devel
>or, via email, send a message with subject or body 'help' to
>	iax...@li...
>
>You can reach the person managing the list at
>	iax...@li...
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Iaxclient-devel digest..."
>
>
>Today's Topics:
>
>    1. RE: Compiling with MinGW/Cygwin (Uriel Carrasquilla)
>    2. RE: Compiling with MinGW/Cygwin (Uriel Carrasquilla)
>
>--__--__--
>
>Message: 1
>Reply-To: <ur...@ad...>
>From: "Uriel Carrasquilla" <ur...@ad...>
>To: "'Steve Kann'" <st...@st...>
>Cc: "'iaxclient devel'" <iax...@li...>
>Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin
>Date: Wed, 11 Jun 2003 21:05:43 -0400
>
>This is a multi-part message in MIME format.
>
>------=_NextPart_000_00F2_01C3305D.39664000
>Content-Type: text/plain;
>	charset="utf-8"
>Content-Transfer-Encoding: quoted-printable
>
>Steve:
>you hit the nail on the head.  I had renamed mingw make file to make.  =
>This is because when I executed "make" from the bash shell interface it =
>could not find make.  Let me try to figure out what I did wrong with my =
>Cygwin install.
>Uriel
>   -----Original Message-----
>   From: Steve Kann [mailto:st...@st...]
>   Sent: Wednesday, June 11, 2003 7:34 PM
>   To: ur...@ad...
>   Cc: iaxclient devel
>   Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin
>
>
>   On Wed, 2003-06-11 at 19:55, Uriel Carrasquilla wrote:=20
>     Steve:
>     My first step: went to ieaxclient/lib, typed: "make clean"=20
>     Results: +ve
>     My second step: from iaxclient/lib typed: "make"
>     Resulting message:
>     failed make (e=3D2): the system cannot find the file specified =
>c"\MinGW\bin\make.exe **** [gsm/src/add.o] Error 2=20
>
>   hmm, OK, this is interesting. =20
>
>   Your build environment is different from mine, in that you're using a =
>"make" provided by MinGW, as opposed to the cygwin make.  Their make =
>might be broken in some way, although I think someone built sucessfully =
>with MinGW with "msys" installed.
>
>   The way my environment is set up, I have cygwin installed, and MinGW =
>installed, and then I have the MinGW tools installed ahead of the cygwin =
>stuff in my path.  I.e. my path is:
>
>
>     =
>/cygdrive/c/MINGW/bin:/usr/local/bin:/usr/bin:/bin:/cygdrive/c/SPRY/BIN:/=
>cygdriv
>     =
>e/c/WINDOWS:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS/system32/WBE=
>M:/cygd
>     rive/c/Program Files/Real/Helix Producer Basic:/cygdrive/c/Program =
>Files/Microso
>     ft Visual Studio/Common/Tools/WinNT:/cygdrive/c/Program =
>Files/Microsoft Visual S
>     tudio/Common/MSDev98/Bin:/cygdrive/c/Program Files/Microsoft Visual =
>Studio/Commo
>     n/Tools:/cygdrive/c/Program Files/Microsoft Visual Studio/VC98/bin=20
>
>   (all that's really important is that the MinGW binaries come before =
>the cygwin binaries).
>
>   Then, I run a shell from cygwin (using the icon the cygwin install =
>leaves on the desktop, which gives me a terminal running bash), and do =
>the make from there.
>
>   But, my MINGW directory doesn't have "make.exe" in it.  There's a =
>mingw32-make.exe, but the purposely don't call it "make.exe", because it =
>sucks :)
>
>   I can't understand the particular error your make gave you, but I =
>don't know what file it's talking about.  (I think the note is that it's =
>trying to make gsm/src/add.o, which is should do from the implicit rule =
>from gsm/src/add.c).
>
>
>   So, I think the easiest way to get you going is to get yourself cygwin =
>(just run http://cygwin.com/setup.exe), find out what that make you're =
>using is and get rid of it, then build with cygwin's tools (except for =
>the compiler, for that use mingw).
>
>   The rest of your research, below, is unlikely to get you anywhere =
>helpful.  I don't maintain any of the other Makefiles other than =
>lib/Makefile simpleclient/testcall/Makefile and =
>simpleclient/wx/Makefile.  Even if those other Makefiles work, they'll =
>give you some library which isn't going to help you.
>
>
>   Also, please post to the mailing list; other people are working =
>through the same thing (]data[ from IRC, for example, just got a whole =
>"wx.exe" build going himself), and the discussion can either help =
>others, or perhaps others can help you.
>
>   -SteveK
>
>
>     Research:
>     went to iaxclient/lib/gsm/src: there is no add.o, just add.c
>     There is a "makefile" here, so I typed "make clean"; results: +ve
>     =20
>     Hacking: from iaxclient/lib/gsm, typed "make".  Results: +ve
>     Went back to iaxclient/lib typed: "make"
>     Resulting message:
>     The same but with code.o missing instead of add.o
>     =20
>     I will greatly appreciate your guidance through these difficulties.
>     =20
>     =20
>     Regards,
>     Uriel=20
>       -----Original Message-----
>       From: iax...@li... =
>[mailto:iax...@li...]On Behalf Of Steve =
>Kann
>       Sent: Wednesday, June 11, 2003 10:21 AM
>       To: ur...@ad...
>       Cc: iaxclient devel
>       Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin
>
>
>       Uriel,
>
>           There's three "maintained" makefiles within the project.  The =
>Makefile in iaxclient/lib, and the Makefiles in simpleclient/testcall =
>and simpleclient/wx.
>
>       Both of the simpleclient/*/Makefiles will call the Makefile in lib =
>to make the library, as both clients use the library, and thus require =
>the library (libiaxclient.a) to be built.
>
>       So, from clean CVS, you should be able to just go to =
>simpleclient/testcall, and type "make".
>
>       However, if you've tried other things, I'd say you'd be best off =
>going to iaxclient/lib, typing "make clean", then "make".  Then, go to =
>the client you want to make and type "make clean", "make".
>
>       (the client Makefiles won't "clean" the library).
>
>       First, try making "testcall", since for "wx", you'll also need to =
>have wxwindows installed, etc.  Definately a better first step is to =
>compile testcall.
>
>       And yes, there's no install targets in the Makefiles.  You don't =
>need to install the library, and the executable targets are standalone =
>(i.e. for wx, there's "wx.exe" for windows, "wx" for linux, and "wx.app" =
>for MacOSX).
>
>
>
>       On Wed, 2003-06-11 at 00:00, Uriel Carrasquilla wrote:=20
>         Steve:
>         I am having a hard time compiling with MinGW and Gygwin.
>         I downloaded the CVS from Monday night.
>         I went to the /iaxclient/simpleclient/wx  (where there is a =
>Makefile) and typed: make
>         Problems developed in the lib/gsm.  I can see in the wx/Makefile =
>that we are trying to make iaxclient.a from lib/gsm.  So I went over and =
>type
>         make iaxclient.a
>         could not find a file.  So I went to the gsm subdirectory and =
>somewhere in there there was another makefile (lower case which is =
>normally a second choice for make).  I did a make.
>         Went back one leve to lib/gsm and executed make=20
>         Got another file missing. =20
>         =20
>         My question: is there a sequence of "make" that I have to =
>execute?
>         what would it be?
>         I could not see and "install" in any of the Makefile.  is it by =
>design?
>         Regards,
>         Uriel=20
>           -----Original Message-----
>           From: iax...@li... =
>[mailto:iax...@li...]On Behalf Of Steve =
>Kann
>           Sent: Tuesday, June 10, 2003 7:48 PM
>           To: iaxclient devel
>           Subject: [Iaxclient-devel] some updates, and Ideas for =
>contributions..
>
>
>           1) (most relevant): put iax call processing (including audio) =
>into a separate thread.  This helps the most when you do things that =
>block the GUI thread, like resizing the window (Win32 only?).  And it =
>seems to also help the Mac a bit(*)
>
>           (*) The volume meters, implemented with progress bars via =
>wxwindows on the mac, eat a lot of CPU for their animation.  Not that it =
>doesn't look good.  I think that this caused some skips on the Mac.
>
>           2) Fixed the DTMF buttons that I broke sometime today or last =
>night.
>
>           3) Fixed PTT a bit.  (looking for feedback on how this works).
>
>           Also, due to a byproduct of the way I did things, if you =
>enable then disable PTT, you'll also be enabling silence =
>detection/suppression.  This will make the client not spit out any audio =
>frames until the input audio level reaches -40 DB. =20
>
>           There's been a lot of interest here on the list and on IRC =
>from a growing community.  That's cool.  People asked what they can help =
>with, so here's some ideas for adventurous souls:
>
>
>           1) IAX2:  You can build it via my Makefiles by setting =
>IAXVER=3D2 at the top of the =20
>                          library Makefile, or building the library by =
>running "make IAXVER=3D2".  It=20
>                          doesn't work quite right, though, so if someone =
>could try and figure that one=20
>                          out, it would be good.  Once it's working, IAX2 =
>should offer us a bunch of=20
>                          quality improvements, especially over the =
>internet.
>
>           2) Registration:  People out there want this, and it will make =
>the apps/library more    =20
>                          useful to the community.  Shouldn't be too =
>hard, but will need to be a bit    =20
>                          careful about keeping track of calls, sessions, =
>peers, etc.
>
>           3) A maintainer for VC++ Makefiles and/or .dsw files.  I don't =
>know this stuff, and I=20
>                         don't like tools you need your mouse for.  But, =
>if it helps people get more=20
>                         involved, I'm all for keeping a current .dsw/dsp =
>or whatever file in CVS, one=20
>                         for each of the Makefiles, I guess (lib, =
>testcall, wx).
>
>           4) Exposing Audio Settings:  Make controls (library functions =
>and GUI) for enumerating and choosing audio input/output devices.  This =
>may require either moving to the standard portaudio callback interface, =
>or hacking pablio to allow you to choose particular devices.  Also, =
>expose setting the input and output "levels".  It's probably best to =
>allow them to change this while the app is running, so you'll need to =
>close/re-open the audio device, etc.
>
>           5) MacOSX Mono audio problem:  Currently MacOSX audio comes =
>only out of the left channel.  Seems like a portaudio problem to track =
>down.
>
>           6) silence detection / dynamic range compression:  Figure out =
>good values or algorithms to make the client automatically (a) not send =
>any packets when there's no speech, (b) put out good consistent volume =
>when there is speech, even if people don't have consistent =
>microphone/soundcard settings, use laptop microphones or nice headsets.
>
>           7) Additional codec support:  I'd start with uLaw, to make =
>some #iaxclient user happy, but also because it's pretty easy to =
>implement, then also try iLBC and/or Speex.  Probably want one way for =
>the user to choose their preferred codec.
>
>           Hmm, that's a bunch of stuff :)
>
>           If anyone wants to step up for this stuff, let the list know, =
>so we all don't duplicate each other's work.
>
>
>           Happy IAX clienting!
>
>           -SteveK
>
>
>
>
>
>
>
>
>
>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."
>               =20
>
>
>
>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."
>           =20
>
>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."
>       =20
>
>
>
>
>------=_NextPart_000_00F2_01C3305D.39664000
>Content-Type: text/html;
>	charset="utf-8"
>Content-Transfer-Encoding: quoted-printable
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
><HTML><HEAD>
><META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
>charset=3Dutf-8">
>
>
><META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR></HEAD>
><BODY>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
>class=3D101360401-12062003>Steve:</SPAN></FONT></DIV>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
>class=3D101360401-12062003>you=20
>hit the nail on the head.&nbsp; I had renamed mingw make file to =
>make.&nbsp;=20
>This is because when I executed "make" from the bash shell interface it =
>could=20
>not find make.&nbsp; Let me try to figure out what I did wrong with my =
>Cygwin=20
>install.</SPAN></FONT></DIV>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
>class=3D101360401-12062003>Uriel</SPAN></FONT></DIV>
><BLOCKQUOTE>
>   <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
>face=3DTahoma=20
>   size=3D2>-----Original Message-----<BR><B>From:</B> Steve Kann=20
>   [mailto:st...@st...]<BR><B>Sent:</B> Wednesday, June 11, 2003 =
>7:34=20
>   PM<BR><B>To:</B> ur...@ad...<BR><B>Cc:</B> iaxclient=20
>   devel<BR><B>Subject:</B> RE: [Iaxclient-devel] Compiling with=20
>   MinGW/Cygwin<BR><BR></DIV></FONT>On Wed, 2003-06-11 at 19:55, Uriel=20
>   Carrasquilla wrote:=20
>   <BLOCKQUOTE TYPE=3D"CITE"><FONT size=3D2><I>Steve:<BR>My first step: =
>went to=20
>     ieaxclient/lib, typed: "make clean" <BR>Results: +ve<BR>My second =
>step: from=20
>     iaxclient/lib typed: "make"<BR>Resulting message:<BR>failed make =
>(e=3D2): the=20
>     system cannot find the file specified c"\MinGW\bin\make.exe ****=20
>     [gsm/src/add.o] Error 2</I></FONT> </BLOCKQUOTE><FONT =
>size=3D2><BR>hmm, OK, this=20
>   is interesting.&nbsp; <BR><BR>Your build environment is different from =
>mine,=20
>   in that you're using a "make" provided by MinGW, as opposed to the =
>cygwin=20
>   make.&nbsp; Their make might be broken in some way, although I think =
>someone=20
>   built sucessfully with MinGW with "msys" installed.<BR><BR>The way my=20
>   environment is set up, I have cygwin installed, and MinGW installed, =
>and then=20
>   I have the MinGW tools installed ahead of the cygwin stuff in my =
>path.&nbsp;=20
>   I.e. my path is:<BR><BR>
>   =
><BLOCKQUOTE>/cygdrive/c/MINGW/bin:/usr/local/bin:/usr/bin:/bin:/cygdrive/=
>c/SPRY/BIN:/cygdriv<BR>e/c/WINDOWS:/cygdrive/c/WINDOWS/system32:/cygdrive=
>/c/WINDOWS/system32/WBEM:/cygd<BR>rive/c/Program=20
>     Files/Real/Helix Producer Basic:/cygdrive/c/Program =
>Files/Microso<BR>ft=20
>     Visual Studio/Common/Tools/WinNT:/cygdrive/c/Program Files/Microsoft =
>Visual=20
>     S<BR>tudio/Common/MSDev98/Bin:/cygdrive/c/Program Files/Microsoft =
>Visual=20
>     Studio/Commo<BR>n/Tools:/cygdrive/c/Program Files/Microsoft Visual=20
>     Studio/VC98/bin </BLOCKQUOTE><BR>(all that's really important is =
>that the=20
>   MinGW binaries come before the cygwin binaries).<BR><BR>Then, I run a =
>shell=20
>   from cygwin (using the icon the cygwin install leaves on the desktop, =
>which=20
>   gives me a terminal running bash), and do the make from =
>there.<BR><BR>But, my=20
>   MINGW directory doesn't have "make.exe" in it.&nbsp; There's a=20
>   mingw32-make.exe, but the purposely don't call it "make.exe", because =
>it sucks=20
>   :)<BR><BR>I can't understand the particular error your make gave you, =
>but I=20
>   don't know what file it's talking about.&nbsp; (I think the note is =
>that it's=20
>   trying to make gsm/src/add.o, which is should do from the implicit =
>rule from=20
>   gsm/src/add.c).<BR><BR><BR>So, I think the easiest way to get you =
>going is to=20
>   get yourself cygwin (just run </FONT><A=20
>   href=3D"http://cygwin.com/setup.exe"><FONT=20
>   size=3D2>http://cygwin.com/setup.exe</FONT></A><FONT size=3D2>), find =
>out what=20
>   that make you're using is and get rid of it, then build with cygwin's =
>tools=20
>   (except for the compiler, for that use mingw).<BR><BR>The rest of your =
>
>   research, below, is unlikely to get you anywhere helpful.&nbsp; I =
>don't=20
>   maintain any of the other Makefiles other than lib/Makefile=20
>   simpleclient/testcall/Makefile and simpleclient/wx/Makefile.&nbsp; =
>Even if=20
>   those other Makefiles work, they'll give you some library which isn't =
>going to=20
>   help you.<BR><BR><BR>Also, please post to the mailing list; other =
>people are=20
>   working through the same thing (]data[ from IRC, for example, just got =
>a whole=20
>   "wx.exe" build going himself), and the discussion can either help =
>others, or=20
>   perhaps others can help you.<BR><BR>-SteveK<BR></FONT><BR>
>   <BLOCKQUOTE TYPE=3D"CITE"><FONT size=3D2><I>Research:<BR>went to=20
>     iaxclient/lib/gsm/src: there is no add.o, just add.c<BR>There is a=20
>     "makefile" here, so I typed "make clean"; results: =
>+ve</FONT><BR><FONT=20
>     color=3D#737373>&nbsp;</FONT><BR><FONT size=3D2>Hacking: from =
>iaxclient/lib/gsm,=20
>     typed "make".&nbsp; Results: +ve<BR>Went back to iaxclient/lib =
>typed:=20
>     "make"<BR>Resulting message:<BR>The same but with code.o missing =
>instead of=20
>     add.o</FONT><BR><FONT color=3D#737373>&nbsp;</FONT><BR><FONT =
>size=3D2>I will=20
>     greatly appreciate your guidance through these =
>difficulties.</FONT><BR><FONT=20
>     color=3D#737373>&nbsp;<BR>&nbsp;</FONT><BR><FONT=20
>     size=3D2>Regards,<BR>Uriel</FONT>=20
>     <BLOCKQUOTE><FONT color=3D#737373 size=3D2>-----Original=20
>       Message-----<BR><B>From:</B> =
>iax...@li...=20
>       [mailto:iax...@li...]<B>On Behalf =
>Of=20
>       </B>Steve Kann<BR><B>Sent:</B> Wednesday, June 11, 2003 10:21=20
>       AM<BR><B>To:</B> ur...@ad...<BR><B>Cc:</B> iaxclient=20
>       devel<BR><B>Subject:</B> RE: [Iaxclient-devel] Compiling with=20
>       MinGW/Cygwin<BR><BR></FONT><BR><FONT=20
>       color=3D#737373>Uriel,<BR><BR>&nbsp;&nbsp;&nbsp; There's three =
>"maintained"=20
>       makefiles within the project.&nbsp; The Makefile in iaxclient/lib, =
>and the=20
>       Makefiles in simpleclient/testcall and =
>simpleclient/wx.<BR><BR>Both of the=20
>       simpleclient/*/Makefiles will call the Makefile in lib to make the =
>
>       library, as both clients use the library, and thus require the =
>library=20
>       (libiaxclient.a) to be built.<BR><BR>So, from clean CVS, you =
>should be=20
>       able to just go to simpleclient/testcall, and type =
>"make".<BR><BR>However,=20
>       if you've tried other things, I'd say you'd be best off going to=20
>       iaxclient/lib, typing "make clean", then "make".&nbsp; Then, go to =
>the=20
>       client you want to make and type "make clean", "make".<BR><BR>(the =
>client=20
>       Makefiles won't "clean" the library).<BR><BR>First, try making =
>"testcall",=20
>       since for "wx", you'll also need to have wxwindows installed, =
>etc.&nbsp;=20
>       Definately a better first step is to compile testcall.<BR><BR>And =
>yes,=20
>       there's no install targets in the Makefiles.&nbsp; You don't need =
>to=20
>       install the library, and the executable targets are standalone =
>(i.e. for=20
>       wx, there's "wx.exe" for windows, "wx" for linux, and "wx.app" for =
>
>       MacOSX).<BR><BR><BR><BR>On Wed, 2003-06-11 at 00:00, Uriel =
>Carrasquilla=20
>       wrote: </FONT>
>       <BLOCKQUOTE TYPE=3D"CITE"><FONT color=3D#737373 =
>size=3D2>Steve:<BR>I am having=20
>         a hard time compiling with MinGW and Gygwin.<BR>I downloaded the =
>CVS=20
>         from Monday night.<BR>I went to the =
>/iaxclient/simpleclient/wx&nbsp;=20
>         (where there is a Makefile) and typed: make<BR>Problems =
>developed in the=20
>         lib/gsm.&nbsp; I can see in the wx/Makefile that we are trying =
>to make=20
>         iaxclient.a from lib/gsm.&nbsp; So I went over and type<BR>make=20
>         iaxclient.a<BR>could not find a file.&nbsp; So I went to the gsm =
>
>         subdirectory and somewhere in there there was another makefile =
>(lower=20
>         case which is normally a second choice for make).&nbsp; I did a=20
>         make.<BR>Went back one leve to lib/gsm and executed make <BR>Got =
>another=20
>         file missing.&nbsp; </FONT><BR><FONT=20
>         color=3D#737373>&nbsp;</FONT><BR><FONT color=3D#737373 =
>size=3D2>My question:=20
>         is there a sequence of "make" that I have to execute?<BR>what =
>would it=20
>         be?<BR>I could not see and "install" in any of the =
>Makefile.&nbsp; is it=20
>         by design?<BR>Regards,<BR>Uriel=20
>         <BLOCKQUOTE>-----Original Message-----<BR><B>From:</B>=20
>           iax...@li...=20
>           [mailto:iax...@li...]<B>On =
>Behalf Of=20
>           </B>Steve Kann<BR><B>Sent:</B> Tuesday, June 10, 2003 7:48=20
>           PM<BR><B>To:</B> iaxclient devel<BR><B>Subject:</B> =
>[Iaxclient-devel]=20
>           some updates, and Ideas for =
>contributions..<BR></FONT><BR><FONT=20
>           color=3D#737373><BR>1) (most relevant): put iax call =
>processing=20
>           (including audio) into a separate thread.&nbsp; This helps the =
>most=20
>           when you do things that block the GUI thread, like resizing =
>the window=20
>           (Win32 only?).&nbsp; And it seems to also help the Mac a=20
>           bit(*)<BR><BR>(*) The volume meters, implemented with progress =
>bars=20
>           via wxwindows on the mac, eat a lot of CPU for their =
>animation.&nbsp;=20
>           Not that it doesn't look good.&nbsp; I think that this caused =
>some=20
>           skips on the Mac.<BR><BR>2) Fixed the DTMF buttons that I =
>broke=20
>           sometime today or last night.<BR><BR>3) Fixed PTT a bit.&nbsp; =
>
>           (looking for feedback on how this works).<BR><BR>Also, due to =
>a=20
>           byproduct of the way I did things, if you enable then disable =
>PTT,=20
>           you'll also be enabling silence detection/suppression.&nbsp; =
>This will=20
>           make the client not spit out any audio frames until the input =
>audio=20
>           level reaches -40 DB.&nbsp; <BR><BR>There's been a lot of =
>interest=20
>           here on the list and on IRC from a growing community.&nbsp; =
>That's=20
>           cool.&nbsp; People asked what they can help with, so here's =
>some ideas=20
>           for adventurous souls:<BR><BR><BR>1) IAX2:&nbsp; You can build =
>it via=20
>           my Makefiles by setting IAXVER=3D2 at the top of the&nbsp;=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           library Makefile, or building the library by running "make=20
>           IAXVER=3D2".&nbsp; It=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           doesn't work quite right, though, so if someone could try and =
>figure=20
>           that one=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           out, it would be good.&nbsp; Once it's working, IAX2 should =
>offer us a=20
>           bunch of=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           quality improvements, especially over the internet.<BR><BR>2)=20
>           Registration:&nbsp; People out there want this, and it will =
>make the=20
>           apps/library more&nbsp;&nbsp;&nbsp;&nbsp;=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           useful to the community.&nbsp; Shouldn't be too hard, but will =
>need to=20
>           be a bit&nbsp;&nbsp;&nbsp;&nbsp;=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           careful about keeping track of calls, sessions, peers, =
>etc.<BR><BR>3)=20
>           A maintainer for VC++ Makefiles and/or .dsw files.&nbsp; I =
>don't know=20
>           this stuff, and I=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;=20
>           don't like tools you need your mouse for.&nbsp; But, if it =
>helps=20
>           people get more=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;=20
>           involved, I'm all for keeping a current .dsw/dsp or whatever =
>file in=20
>           CVS, one=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;=20
>           for each of the Makefiles, I guess (lib, testcall, =
>wx).<BR><BR>4)=20
>           Exposing Audio Settings:&nbsp; Make controls (library =
>functions and=20
>           GUI) for enumerating and choosing audio input/output =
>devices.&nbsp;=20
>           This may require either moving to the standard portaudio =
>callback=20
>           interface, or hacking pablio to allow you to choose particular =
>
>           devices.&nbsp; Also, expose setting the input and output=20
>           "levels".&nbsp; It's probably best to allow them to change =
>this while=20
>           the app is running, so you'll need to close/re-open the audio =
>device,=20
>           etc.<BR><BR>5) MacOSX Mono audio problem:&nbsp; Currently =
>MacOSX audio=20
>           comes only out of the left channel.&nbsp; Seems like a =
>portaudio=20
>           problem to track down.<BR><BR>6) silence detection / dynamic =
>range=20
>           compression:&nbsp; Figure out good values or algorithms to =
>make the=20
>           client automatically (a) not send any packets when there's no =
>speech,=20
>           (b) put out good consistent volume when there is speech, even =
>if=20
>           people don't have consistent microphone/soundcard settings, =
>use laptop=20
>           microphones or nice headsets.<BR><BR>7) Additional codec=20
>           support:&nbsp; I'd start with uLaw, to make some #iaxclient =
>user=20
>           happy, but also because it's pretty easy to implement, then =
>also try=20
>           iLBC and/or Speex.&nbsp; Probably want one way for the user to =
>choose=20
>           their preferred codec.<BR><BR>Hmm, that's a bunch of stuff=20
>           :)<BR><BR>If anyone wants to step up for this stuff, let the =
>list=20
>           know, so we all don't duplicate each other's =
>work.<BR><BR><BR>Happy=20
>           IAX =
>clienting!<BR><BR>-SteveK<BR><BR><BR><BR><BR></I></FONT><BR>
>           <TABLE cellPadding=3D0 cellSpacing=3D0 width=3D"100%">
>             <TBODY>
>             <TR></TR>
>             <TR></TR>
>             <TR></TR>
>             <TR></TR>
>             <TR>
>               <TD><PRE>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."</PRE></TD></TR></TBODY></TABLE></BLOCKQUOTE></BLOCKQUOTE>
>       <TABLE cellPadding=3D0 cellSpacing=3D0 width=3D"100%">
>         <TBODY>
>         <TR></TR>
>         <TR></TR>
>         <TR>
>           <TD><PRE>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."</PRE></TD></TR></TBODY></TABLE></BLOCKQUOTE></BLOCKQUOTE>
>   <TABLE cellPadding=3D0 cellSpacing=3D0 width=3D"100%">
>     <TBODY>
>     <TR>
>       <TD><PRE>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."</PRE></TD></TR></TBODY></TABLE><BR><FONT=20
>   color=3D#737373><I></I></FONT><BR></BLOCKQUOTE></BODY></HTML>
>
>------=_NextPart_000_00F2_01C3305D.39664000--
>
>
>
>
>--__--__--
>
>Message: 2
>Reply-To: <ur...@ad...>
>From: "Uriel Carrasquilla" <ur...@ad...>
>To: "'Steve Kann'" <st...@st...>
>Cc: "'iaxclient devel'" <iax...@li...>
>Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin
>Date: Wed, 11 Jun 2003 22:41:34 -0400
>
>This is a multi-part message in MIME format.
>
>------=_NextPart_000_00F8_01C3306A.9DF91800
>Content-Type: text/plain;
>	charset="utf-8"
>Content-Transfer-Encoding: quoted-printable
>
>Steve:
>It is now working with the "make" from Cygwin.  I had to download it =
>from http://cygwin.com/setup.exe as it is not part of the default =
>install.
>I was able to compile with "make clena" followed by "make" under =
>iaxclient/simpleclient/testcall.  It works and I tested it and modified =
>it to use my own *.  There was quite a bit of noise and quite a bit of =
>delay but it is very promissing.
>Then I got ambitious and tried the same steps undex =
>iaxclient/simpleclient/wx.  I watched in horror the screen go for quite =
>a while.  Then it stopped with a message "1 error in wx.o".  I tried to =
>redirect the output to file so I could attach it here but only got the =
>first few lines of the "Makefile" execution.  Then, when the Cygwin make =
>takes over, it all went back to the STD output, my screen.
>Since I made it this far, I am now more committed than ever.
>Did I miss a step to compile the "GUI" version?
>Regards,
>Uriel
>   -----Original Message-----
>   From: iax...@li... =
>[mailto:iax...@li...]On Behalf Of Steve =
>Kann
>   Sent: Wednesday, June 11, 2003 7:34 PM
>   To: ur...@ad...
>   Cc: iaxclient devel
>   Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin
>
>
>   On Wed, 2003-06-11 at 19:55, Uriel Carrasquilla wrote:=20
>     Steve:
>     My first step: went to ieaxclient/lib, typed: "make clean"=20
>     Results: +ve
>     My second step: from iaxclient/lib typed: "make"
>     Resulting message:
>     failed make (e=3D2): the system cannot find the file specified =
>c"\MinGW\bin\make.exe **** [gsm/src/add.o] Error 2=20
>
>   hmm, OK, this is interesting. =20
>
>   Your build environment is different from mine, in that you're using a =
>"make" provided by MinGW, as opposed to the cygwin make.  Their make =
>might be broken in some way, although I think someone built sucessfully =
>with MinGW with "msys" installed.
>
>   The way my environment is set up, I have cygwin installed, and MinGW =
>installed, and then I have the MinGW tools installed ahead of the cygwin =
>stuff in my path.  I.e. my path is:
>
>
>     =
>/cygdrive/c/MINGW/bin:/usr/local/bin:/usr/bin:/bin:/cygdrive/c/SPRY/BIN:/=
>cygdriv
>     =
>e/c/WINDOWS:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS/system32/WBE=
>M:/cygd
>     rive/c/Program Files/Real/Helix Producer Basic:/cygdrive/c/Program =
>Files/Microso
>     ft Visual Studio/Common/Tools/WinNT:/cygdrive/c/Program =
>Files/Microsoft Visual S
>     tudio/Common/MSDev98/Bin:/cygdrive/c/Program Files/Microsoft Visual =
>Studio/Commo
>     n/Tools:/cygdrive/c/Program Files/Microsoft Visual Studio/VC98/bin=20
>
>   (all that's really important is that the MinGW binaries come before =
>the cygwin binaries).
>
>   Then, I run a shell from cygwin (using the icon the cygwin install =
>leaves on the desktop, which gives me a terminal running bash), and do =
>the make from there.
>
>   But, my MINGW directory doesn't have "make.exe" in it.  There's a =
>mingw32-make.exe, but the purposely don't call it "make.exe", because it =
>sucks :)
>
>   I can't understand the particular error your make gave you, but I =
>don't know what file it's talking about.  (I think the note is that it's =
>trying to make gsm/src/add.o, which is should do from the implicit rule =
>from gsm/src/add.c).
>
>
>   So, I think the easiest way to get you going is to get yourself cygwin =
>(just run http://cygwin.com/setup.exe), find out what that make you're =
>using is and get rid of it, then build with cygwin's tools (except for =
>the compiler, for that use mingw).
>
>   The rest of your research, below, is unlikely to get you anywhere =
>helpful.  I don't maintain any of the other Makefiles other than =
>lib/Makefile simpleclient/testcall/Makefile and =
>simpleclient/wx/Makefile.  Even if those other Makefiles work, they'll =
>give you some library which isn't going to help you.
>
>
>   Also, please post to the mailing list; other people are working =
>through the same thing (]data[ from IRC, for example, just got a whole =
>"wx.exe" build going himself), and the discussion can either help =
>others, or perhaps others can help you.
>
>   -SteveK
>
>
>     Research:
>     went to iaxclient/lib/gsm/src: there is no add.o, just add.c
>     There is a "makefile" here, so I typed "make clean"; results: +ve
>     =20
>     Hacking: from iaxclient/lib/gsm, typed "make".  Results: +ve
>     Went back to iaxclient/lib typed: "make"
>     Resulting message:
>     The same but with code.o missing instead of add.o
>     =20
>     I will greatly appreciate your guidance through these difficulties.
>     =20
>     =20
>     Regards,
>     Uriel=20
>       -----Original Message-----
>       From: iax...@li... =
>[mailto:iax...@li...]On Behalf Of Steve =
>Kann
>       Sent: Wednesday, June 11, 2003 10:21 AM
>       To: ur...@ad...
>       Cc: iaxclient devel
>       Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin
>
>
>       Uriel,
>
>           There's three "maintained" makefiles within the project.  The =
>Makefile in iaxclient/lib, and the Makefiles in simpleclient/testcall =
>and simpleclient/wx.
>
>       Both of the simpleclient/*/Makefiles will call the Makefile in lib =
>to make the library, as both clients use the library, and thus require =
>the library (libiaxclient.a) to be built.
>
>       So, from clean CVS, you should be able to just go to =
>simpleclient/testcall, and type "make".
>
>       However, if you've tried other things, I'd say you'd be best off =
>going to iaxclient/lib, typing "make clean", then "make".  Then, go to =
>the client you want to make and type "make clean", "make".
>
>       (the client Makefiles won't "clean" the library).
>
>       First, try making "testcall", since for "wx", you'll also need to =
>have wxwindows installed, etc.  Definately a better first step is to =
>compile testcall.
>
>       And yes, there's no install targets in the Makefiles.  You don't =
>need to install the library, and the executable targets are standalone =
>(i.e. for wx, there's "wx.exe" for windows, "wx" for linux, and "wx.app" =
>for MacOSX).
>
>
>
>       On Wed, 2003-06-11 at 00:00, Uriel Carrasquilla wrote:=20
>         Steve:
>         I am having a hard time compiling with MinGW and Gygwin.
>         I downloaded the CVS from Monday night.
>         I went to the /iaxclient/simpleclient/wx  (where there is a =
>Makefile) and typed: make
>         Problems developed in the lib/gsm.  I can see in the wx/Makefile =
>that we are trying to make iaxclient.a from lib/gsm.  So I went over and =
>type
>         make iaxclient.a
>         could not find a file.  So I went to the gsm subdirectory and =
>somewhere in there there was another makefile (lower case which is =
>normally a second choice for make).  I did a make.
>         Went back one leve to lib/gsm and executed make=20
>         Got another file missing. =20
>         =20
>         My question: is there a sequence of "make" that I have to =
>execute?
>         what would it be?
>         I could not see and "install" in any of the Makefile.  is it by =
>design?
>         Regards,
>         Uriel=20
>           -----Original Message-----
>           From: iax...@li... =
>[mailto:iax...@li...]On Behalf Of Steve =
>Kann
>           Sent: Tuesday, June 10, 2003 7:48 PM
>           To: iaxclient devel
>           Subject: [Iaxclient-devel] some updates, and Ideas for =
>contributions..
>
>
>           1) (most relevant): put iax call processing (including audio) =
>into a separate thread.  This helps the most when you do things that =
>block the GUI thread, like resizing the window (Win32 only?).  And it =
>seems to also help the Mac a bit(*)
>
>           (*) The volume meters, implemented with progress bars via =
>wxwindows on the mac, eat a lot of CPU for their animation.  Not that it =
>doesn't look good.  I think that this caused some skips on the Mac.
>
>           2) Fixed the DTMF buttons that I broke sometime today or last =
>night.
>
>           3) Fixed PTT a bit.  (looking for feedback on how this works).
>
>           Also, due to a byproduct of the way I did things, if you =
>enable then disable PTT, you'll also be enabling silence =
>detection/suppression.  This will make the client not spit out any audio =
>frames until the input audio level reaches -40 DB. =20
>
>           There's been a lot of interest here on the list and on IRC =
>from a growing community.  That's cool.  People asked what they can help =
>with, so here's some ideas for adventurous souls:
>
>
>           1) IAX2:  You can build it via my Makefiles by setting =
>IAXVER=3D2 at the top of the =20
>                          library Makefile, or building the library by =
>running "make IAXVER=3D2".  It=20
>                          doesn't work quite right, though, so if someone =
>could try and figure that one=20
>                          out, it would be good.  Once it's working, IAX2 =
>should offer us a bunch of=20
>                          quality improvements, especially over the =
>internet.
>
>           2) Registration:  People out there want this, and it will make =
>the apps/library more    =20
>                          useful to the community.  Shouldn't be too =
>hard, but will need to be a bit    =20
>                          careful about keeping track of calls, sessions, =
>peers, etc.
>
>           3) A maintainer for VC++ Makefiles and/or .dsw files.  I don't =
>know this stuff, and I=20
>                         don't like tools you need your mouse for.  But, =
>if it helps people get more=20
>                         involved, I'm all for keeping a current .dsw/dsp =
>or whatever file in CVS, one=20
>                         for each of the Makefiles, I guess (lib, =
>testcall, wx).
>
>           4) Exposing Audio Settings:  Make controls (library functions =
>and GUI) for enumerating and choosing audio input/output devices.  This =
>may require either moving to the standard portaudio callback interface, =
>or hacking pablio to allow you to choose particular devices.  Also, =
>expose setting the input and output "levels".  It's probably best to =
>allow them to change this while the app is running, so you'll need to =
>close/re-open the audio device, etc.
>
>           5) MacOSX Mono audio problem:  Currently MacOSX audio comes =
>only out of the left channel.  Seems like a portaudio problem to track =
>down.
>
>           6) silence detection / dynamic range compression:  Figure out =
>good values or algorithms to make the client automatically (a) not send =
>any packets when there's no speech, (b) put out good consistent volume =
>when there is speech, even if people don't have consistent =
>microphone/soundcard settings, use laptop microphones or nice headsets.
>
>           7) Additional codec support:  I'd start with uLaw, to make =
>some #iaxclient user happy, but also because it's pretty easy to =
>implement, then also try iLBC and/or Speex.  Probably want one way for =
>the user to choose their preferred codec.
>
>           Hmm, that's a bunch of stuff :)
>
>           If anyone wants to step up for this stuff, let the list know, =
>so we all don't duplicate each other's work.
>
>
>           Happy IAX clienting!
>
>           -SteveK
>
>
>
>
>
>
>
>
>
>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."
>               =20
>
>
>
>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."
>           =20
>
>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."
>       =20
>
>
>
>
>------=_NextPart_000_00F8_01C3306A.9DF91800
>Content-Type: text/html;
>	charset="utf-8"
>Content-Transfer-Encoding: quoted-printable
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
><HTML><HEAD>
><META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
>charset=3Dutf-8">
>
>
><META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR></HEAD>
><BODY>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
>class=3D605463302-12062003>Steve:</SPAN></FONT></DIV>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
>class=3D605463302-12062003>It is=20
>now working with the "make" from Cygwin.&nbsp; I had to download it from =
><A=20
>href=3D"http://cygwin.com/setup.exe"><FONT=20
>size=3D2>http://cygwin.com/setup.exe</FONT></A> as it is not part of the =
>default=20
>install.</SPAN></FONT></DIV>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
>class=3D605463302-12062003>I was=20
>able to compile with "make clena" followed by "make" under=20
>iaxclient/simpleclient/testcall.&nbsp; It works and I tested it and =
>modified it=20
>to use my own *.&nbsp; There was quite a bit of noise and quite a bit of =
>delay=20
>but it is very promissing.</SPAN></FONT></DIV>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
>class=3D605463302-12062003>Then I=20
>got ambitious and tried the same steps undex =
>iaxclient/simpleclient/wx.&nbsp; I=20
>watched in horror the screen go for quite a while.&nbsp; Then it stopped =
>with a=20
>message "1 error in wx.o".&nbsp; I tried to redirect the output to file =
>so I=20
>could attach it here but only got the first few lines of the "Makefile"=20
>execution.&nbsp; Then, when the Cygwin make takes over, it all went back =
>to the=20
>STD output, my screen.</SPAN></FONT></DIV>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
>class=3D605463302-12062003>Since=20
>I made it this far, I am now more committed than =
>ever.</SPAN></FONT></DIV>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
>class=3D605463302-12062003>Did I=20
>miss a step to compile the "GUI" version?</SPAN></FONT></DIV>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
>class=3D605463302-12062003>Regards,</SPAN></FONT></DIV>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
>class=3D605463302-12062003>Uriel</SPAN></FONT></DIV>
><BLOCKQUOTE>
>   <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
>face=3DTahoma=20
>   size=3D2>-----Original Message-----<BR><B>From:</B>=20
>   iax...@li...=20
>   [mailto:iax...@li...]<B>On Behalf Of =
></B>Steve=20
>   Kann<BR><B>Sent:</B> Wednesday, June 11, 2003 7:34 PM<BR><B>To:</B>=20
>   ur...@ad...<BR><B>Cc:</B> iaxclient devel<BR><B>Subject:</B> =
>RE:=20
>   [Iaxclient-devel] Compiling with MinGW/Cygwin<BR><BR></DIV></FONT>On =
>Wed,=20
>   2003-06-11 at 19:55, Uriel Carrasquilla wrote:=20
>   <BLOCKQUOTE TYPE=3D"CITE"><FONT size=3D2><I>Steve:<BR>My first step: =
>went to=20
>     ieaxclient/lib, typed: "make clean" <BR>Results: +ve<BR>My second =
>step: from=20
>     iaxclient/lib typed: "make"<BR>Resulting message:<BR>failed make =
>(e=3D2): the=20
>     system cannot find the file specified c"\MinGW\bin\make.exe ****=20
>     [gsm/src/add.o] Error 2</I></FONT> </BLOCKQUOTE><FONT =
>size=3D2><BR>hmm, OK, this=20
>   is interesting.&nbsp; <BR><BR>Your build environment is different from =
>mine,=20
>   in that you're using a "make" provided by MinGW, as opposed to the =
>cygwin=20
>   make.&nbsp; Their make might be broken in some way, although I think =
>someone=20
>   built sucessfully with MinGW with "msys" installed.<BR><BR>The way my=20
>   environment is set up, I have cygwin installed, and MinGW installed, =
>and then=20
>   I have the MinGW tools installed ahead of the cygwin stuff in my =
>path.&nbsp;=20
>   I.e. my path is:<BR><BR>
>   =
><BLOCKQUOTE>/cygdrive/c/MINGW/bin:/usr/local/bin:/usr/bin:/bin:/cygdrive/=
>c/SPRY/BIN:/cygdriv<BR>e/c/WINDOWS:/cygdrive/c/WINDOWS/system32:/cygdrive=
>/c/WINDOWS/system32/WBEM:/cygd<BR>rive/c/Program=20
>     Files/Real/Helix Producer Basic:/cygdrive/c/Program =
>Files/Microso<BR>ft=20
>     Visual Studio/Common/Tools/WinNT:/cygdrive/c/Program Files/Microsoft =
>Visual=20
>     S<BR>tudio/Common/MSDev98/Bin:/cygdrive/c/Program Files/Microsoft =
>Visual=20
>     Studio/Commo<BR>n/Tools:/cygdrive/c/Program Files/Microsoft Visual=20
>     Studio/VC98/bin </BLOCKQUOTE><BR>(all that's really important is =
>that the=20
>   MinGW binaries come before the cygwin binaries).<BR><BR>Then, I run a =
>shell=20
>   from cygwin (using the icon the cygwin install leaves on the desktop, =
>which=20
>   gives me a terminal running bash), and do the make from =
>there.<BR><BR>But, my=20
>   MINGW directory doesn't have "make.exe" in it.&nbsp; There's a=20
>   mingw32-make.exe, but the purposely don't call it "make.exe", because =
>it sucks=20
>   :)<BR><BR>I can't understand the particular error your make gave you, =
>but I=20
>   don't know what file it's talking about.&nbsp; (I think the note is =
>that it's=20
>   trying to make gsm/src/add.o, which is should do from the implicit =
>rule from=20
>   gsm/src/add.c).<BR><BR><BR>So, I think the easiest way to get you =
>going is to=20
>   get yourself cygwin (just run </FONT><A=20
>   href=3D"http://cygwin.com/setup.exe"><FONT=20
>   size=3D2>http://cygwin.com/setup.exe</FONT></A><FONT size=3D2>), find =
>out what=20
>   that make you're using is and get rid of it, then build with cygwin's =
>tools=20
>   (except for the compiler, for that use mingw).<BR><BR>The rest of your =
>
>   research, below, is unlikely to get you anywhere helpful.&nbsp; I =
>don't=20
>   maintain any of the other Makefiles other than lib/Makefile=20
>   simpleclient/testcall/Makefile and simpleclient/wx/Makefile.&nbsp; =
>Even if=20
>   those other Makefiles work, they'll give you some library which isn't =
>going to=20
>   help you.<BR><BR><BR>Also, please post to the mailing list; other =
>people are=20
>   working through the same thing (]data[ from IRC, for example, just got =
>a whole=20
>   "wx.exe" build going himself), and the discussion can either help =
>others, or=20
>   perhaps others can help you.<BR><BR>-SteveK<BR></FONT><BR>
>   <BLOCKQUOTE TYPE=3D"CITE"><FONT size=3D2><I>Research:<BR>went to=20
>     iaxclient/lib/gsm/src: there is no add.o, just add.c<BR>There is a=20
>     "makefile" here, so I typed "make clean"; results: =
>+ve</FONT><BR><FONT=20
>     color=3D#737373>&nbsp;</FONT><BR><FONT size=3D2>Hacking: from =
>iaxclient/lib/gsm,=20
>     typed "make".&nbsp; Results: +ve<BR>Went back to iaxclient/lib =
>typed:=20
>     "make"<BR>Resulting message:<BR>The same but with code.o missing =
>instead of=20
>     add.o</FONT><BR><FONT color=3D#737373>&nbsp;</FONT><BR><FONT =
>size=3D2>I will=20
>     greatly appreciate your guidance through these =
>difficulties.</FONT><BR><FONT=20
>     color=3D#737373>&nbsp;<BR>&nbsp;</FONT><BR><FONT=20
>     size=3D2>Regards,<BR>Uriel</FONT>=20
>     <BLOCKQUOTE><FONT color=3D#737373 size=3D2>-----Original=20
>       Message-----<BR><B>From:</B> =
>iax...@li...=20
>       [mailto:iax...@li...]<B>On Behalf =
>Of=20
>       </B>Steve Kann<BR><B>Sent:</B> Wednesday, June 11, 2003 10:21=20
>       AM<BR><B>To:</B> ur...@ad...<BR><B>Cc:</B> iaxclient=20
>       devel<BR><B>Subject:</B> RE: [Iaxclient-devel] Compiling with=20
>       MinGW/Cygwin<BR><BR></FONT><BR><FONT=20
>       color=3D#737373>Uriel,<BR><BR>&nbsp;&nbsp;&nbsp; There's three =
>"maintained"=20
>       makefiles within the project.&nbsp; The Makefile in iaxclient/lib, =
>and the=20
>       Makefiles in simpleclient/testcall and =
>simpleclient/wx.<BR><BR>Both of the=20
>       simpleclient/*/Makefiles will call the Makefile in lib to make the =
>
>       library, as both clients use the library, and thus require the =
>library=20
>       (libiaxclient.a) to be built.<BR><BR>So, from clean CVS, you =
>should be=20
>       able to just go to simpleclient/testcall, and type =
>"make".<BR><BR>However,=20
>       if you've tried other things, I'd say you'd be best off going to=20
>       iaxclient/lib, typing "make clean", then "make".&nbsp; Then, go to =
>the=20
>       client you want to make and type "make clean", "make".<BR><BR>(the =
>client=20
>       Makefiles won't "clean" the library).<BR><BR>First, try making =
>"testcall",=20
>       since for "wx", you'll also need to have wxwindows installed, =
>etc.&nbsp;=20
>       Definately a better first step is to compile testcall.<BR><BR>And =
>yes,=20
>       there's no install targets in the Makefiles.&nbsp; You don't need =
>to=20
>       install the library, and the executable targets are standalone =
>(i.e. for=20
>       wx, there's "wx.exe" for windows, "wx" for linux, and "wx.app" for =
>
>       MacOSX).<BR><BR><BR><BR>On Wed, 2003-06-11 at 00:00, Uriel =
>Carrasquilla=20
>       wrote: </FONT>
>       <BLOCKQUOTE TYPE=3D"CITE"><FONT color=3D#737373 =
>size=3D2>Steve:<BR>I am having=20
>         a hard time compiling with MinGW and Gygwin.<BR>I downloaded the =
>CVS=20
>         from Monday night.<BR>I went to the =
>/iaxclient/simpleclient/wx&nbsp;=20
>         (where there is a Makefile) and typed: make<BR>Problems =
>developed in the=20
>         lib/gsm.&nbsp; I can see in the wx/Makefile that we are trying =
>to make=20
>         iaxclient.a from lib/gsm.&nbsp; So I went over and type<BR>make=20
>         iaxclient.a<BR>could not find a file.&nbsp; So I went to the gsm =
>
>         subdirectory and somewhere in there there was another makefile =
>(lower=20
>         case which is normally a second choice for make).&nbsp; I did a=20
>         make.<BR>Went back one leve to lib/gsm and executed make <BR>Got =
>another=20
>         file missing.&nbsp; </FONT><BR><FONT=20
>         color=3D#737373>&nbsp;</FONT><BR><FONT color=3D#737373 =
>size=3D2>My question:=20
>         is there a sequence of "make" that I have to execute?<BR>what =
>would it=20
>         be?<BR>I could not see and "install" in any of the =
>Makefile.&nbsp; is it=20
>         by design?<BR>Regards,<BR>Uriel=20
>         <BLOCKQUOTE>-----Original Message-----<BR><B>From:</B>=20
>           iax...@li...=20
>           [mailto:iax...@li...]<B>On =
>Behalf Of=20
>           </B>Steve Kann<BR><B>Sent:</B> Tuesday, June 10, 2003 7:48=20
>           PM<BR><B>To:</B> iaxclient devel<BR><B>Subject:</B> =
>[Iaxclient-devel]=20
>           some updates, and Ideas for =
>contributions..<BR></FONT><BR><FONT=20
>           color=3D#737373><BR>1) (most relevant): put iax call =
>processing=20
>           (including audio) into a separate thread.&nbsp; This helps the =
>most=20
>           when you do things that block the GUI thread, like resizing =
>the window=20
>           (Win32 only?).&nbsp; And it seems to also help the Mac a=20
>           bit(*)<BR><BR>(*) The volume meters, implemented with progress =
>bars=20
>           via wxwindows on the mac, eat a lot of CPU for their =
>animation.&nbsp;=20
>           Not that it doesn't look good.&nbsp; I think that this caused =
>some=20
>           skips on the Mac.<BR><BR>2) Fixed the DTMF buttons that I =
>broke=20
>           sometime today or last night.<BR><BR>3) Fixed PTT a bit.&nbsp; =
>
>           (looking for feedback on how this works).<BR><BR>Also, due to =
>a=20
>           byproduct of the way I did things, if you enable then disable =
>PTT,=20
>           you'll also be enabling silence detection/suppression.&nbsp; =
>This will=20
>           make the client not spit out any audio frames until the input =
>audio=20
>           level reaches -40 DB.&nbsp; <BR><BR>There's been a lot of =
>interest=20
>           here on the list and on IRC from a growing community.&nbsp; =
>That's=20
>           cool.&nbsp; People asked what they can help with, so here's =
>some ideas=20
>           for adventurous souls:<BR><BR><BR>1) IAX2:&nbsp; You can build =
>it via=20
>           my Makefiles by setting IAXVER=3D2 at the top of the&nbsp;=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           library Makefile, or building the library by running "make=20
>           IAXVER=3D2".&nbsp; It=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           doesn't work quite right, though, so if someone could try and =
>figure=20
>           that one=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           out, it would be good.&nbsp; Once it's working, IAX2 should =
>offer us a=20
>           bunch of=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           quality improvements, especially over the internet.<BR><BR>2)=20
>           Registration:&nbsp; People out there want this, and it will =
>make the=20
>           apps/library more&nbsp;&nbsp;&nbsp;&nbsp;=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           useful to the community.&nbsp; Shouldn't be too hard, but will =
>need to=20
>           be a bit&nbsp;&nbsp;&nbsp;&nbsp;=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           careful about keeping track of calls, sessions, peers, =
>etc.<BR><BR>3)=20
>           A maintainer for VC++ Makefiles and/or .dsw files.&nbsp; I =
>don't know=20
>           this stuff, and I=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;=20
>           don't like tools you need your mouse for.&nbsp; But, if it =
>helps=20
>           people get more=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;=20
>           involved, I'm all for keeping a current .dsw/dsp or whatever =
>file in=20
>           CVS, one=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;=20
>           for each of the Makefiles, I guess (lib, testcall, =
>wx).<BR><BR>4)=20
>           Exposing Audio Settings:&nbsp; Make controls (library =
>functions and=20
>           GUI) for enumerating and choosing audio input/output =
>devices.&nbsp;=20
>           This may require either moving to the standard portaudio =
>callback=20
>           interface, or hacking pablio to allow you to choose particular =
>
>           devices.&nbsp; Also, expose setting the input and output=20
>           "levels".&nbsp; It's probably best to allow them to change =
>this while=20
>           the app is running, so you'll need to close/re-open the audio =
>device,=20
>           etc.<BR><BR>5) MacOSX Mono audio problem:&nbsp; Currently =
>MacOSX audio=20
>           comes only out of the left channel.&nbsp; Seems like a =
>portaudio=20
>           problem to track down.<BR><BR>6) silence detection / dynamic =
>range=20
>           compression:&nbsp; Figure out good values or algorithms to =
>make the=20
>           client automatically (a) not send any packets when there's no =
>speech,=20
>           (b) put out good consistent volume when there is speech, even =
>if=20
>           people don't have consistent microphone/soundcard settings, =
>use laptop=20
>           microphones or nice headsets.<BR><BR>7) Additional codec=20
>           support:&nbsp; I'd start with uLaw, to make some #iaxclient =
>user=20
>           happy, but also because it's pretty easy to implement, then =
>also try=20
>           iLBC and/or Speex.&nbsp; Probably want one way for the user to =
>choose=20
>           their preferred codec.<BR><BR>Hmm, that's a bunch of stuff=20
>           :)<BR><BR>If anyone wants to step up for this stuff, let the =
>list=20
>           know, so we all don't duplicate each other's =
>work.<BR><BR><BR>Happy=20
>   ...
 
[truncated message content]

[Iaxclient-devel] RE: Compiling with MinGW/Cygwin (an Illogical Solution)

[SYED O. A. <sye...@ho...>]

Hi

Just read the prob lem of Uriel this sort of problem was also happening with 
me and i found very illogical thing .

i have the same configuration as discussed by steve and the have same 
problem as discussed by Uriel :)


so start cygwin , goto /iaxclient/lib and type
mingw32-make -n >script.sh
sh script.h

i dunno why this is happening but it works for me hopefully for others .

Bye




>From: iax...@li...
>Reply-To: iax...@li...
>To: iax...@li...
>Subject: Iaxclient-devel digest, Vol 1 #19 - 2 msgs
>Date: Wed, 11 Jun 2003 19:04:08 -0700
>MIME-Version: 1.0
>Received: from sc8-sf-list2.sourceforge.net ([66.35.250.206]) by 
>mc7-f3.law1.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Wed, 11 Jun 
>2003 19:05:05 -0700
>Received: from sc8-sf-list1-b.sourceforge.net ([10.3.1.13] 
>helo=sc8-sf-list1.sourceforge.net)by sc8-sf-list2.sourceforge.net with 
>esmtp (Exim 3.31-VA-mm2 #1 (Debian))id 19QHSw-0008QL-00; Wed, 11 Jun 2003 
>19:05:26 -0700
>X-Message-Info: JGTYoYF78jEHjJx36Oi8+Q1OJDRSDidP
>X-Mailer: Mailman v2.0.9-sf.net
>Sender: iax...@li...
>Errors-To: iax...@li...
>X-BeenThere: iax...@li...
>X-Mailman-Version: 2.0.9-sf.net
>Precedence: bulk
>List-Help: 
><mailto:iax...@li...?subject=help>
>List-Post: <mailto:iax...@li...>
>List-Subscribe: 
><https://lists.sourceforge.net/lists/listinfo/iaxclient-devel>,<mailto:iax...@li...?subject=subscribe>
>List-Id: Discussion of development of Cross-platform IAX clients 
><iaxclient-devel.lists.sourceforge.net>
>List-Unsubscribe: 
><https://lists.sourceforge.net/lists/listinfo/iaxclient-devel>,<mailto:iax...@li...?subject=unsubscribe>
>List-Archive: 
><http://sourceforge.net/mailarchive/forum.php?forum=iaxclient-devel>
>Message-Id: <E19...@sc...>
>Return-Path: iax...@li...
>X-OriginalArrivalTime: 12 Jun 2003 02:05:05.0460 (UTC) 
>FILETIME=[0AB10F40:01C33087]
>
>Send Iaxclient-devel mailing list submissions to
>	iax...@li...
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	https://lists.sourceforge.net/lists/listinfo/iaxclient-devel
>or, via email, send a message with subject or body 'help' to
>	iax...@li...
>
>You can reach the person managing the list at
>	iax...@li...
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Iaxclient-devel digest..."
>
>
>Today's Topics:
>
>    1. RE: Compiling with MinGW/Cygwin (Uriel Carrasquilla)
>    2. RE: Compiling with MinGW/Cygwin (Uriel Carrasquilla)
>
>--__--__--
>
>Message: 1
>Reply-To: <ur...@ad...>
>From: "Uriel Carrasquilla" <ur...@ad...>
>To: "'Steve Kann'" <st...@st...>
>Cc: "'iaxclient devel'" <iax...@li...>
>Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin
>Date: Wed, 11 Jun 2003 21:05:43 -0400
>
>This is a multi-part message in MIME format.
>
>------=_NextPart_000_00F2_01C3305D.39664000
>Content-Type: text/plain;
>	charset="utf-8"
>Content-Transfer-Encoding: quoted-printable
>
>Steve:
>you hit the nail on the head.  I had renamed mingw make file to make.  =
>This is because when I executed "make" from the bash shell interface it =
>could not find make.  Let me try to figure out what I did wrong with my =
>Cygwin install.
>Uriel
>   -----Original Message-----
>   From: Steve Kann [mailto:st...@st...]
>   Sent: Wednesday, June 11, 2003 7:34 PM
>   To: ur...@ad...
>   Cc: iaxclient devel
>   Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin
>
>
>   On Wed, 2003-06-11 at 19:55, Uriel Carrasquilla wrote:=20
>     Steve:
>     My first step: went to ieaxclient/lib, typed: "make clean"=20
>     Results: +ve
>     My second step: from iaxclient/lib typed: "make"
>     Resulting message:
>     failed make (e=3D2): the system cannot find the file specified =
>c"\MinGW\bin\make.exe **** [gsm/src/add.o] Error 2=20
>
>   hmm, OK, this is interesting. =20
>
>   Your build environment is different from mine, in that you're using a =
>"make" provided by MinGW, as opposed to the cygwin make.  Their make =
>might be broken in some way, although I think someone built sucessfully =
>with MinGW with "msys" installed.
>
>   The way my environment is set up, I have cygwin installed, and MinGW =
>installed, and then I have the MinGW tools installed ahead of the cygwin =
>stuff in my path.  I.e. my path is:
>
>
>     =
>/cygdrive/c/MINGW/bin:/usr/local/bin:/usr/bin:/bin:/cygdrive/c/SPRY/BIN:/=
>cygdriv
>     =
>e/c/WINDOWS:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS/system32/WBE=
>M:/cygd
>     rive/c/Program Files/Real/Helix Producer Basic:/cygdrive/c/Program =
>Files/Microso
>     ft Visual Studio/Common/Tools/WinNT:/cygdrive/c/Program =
>Files/Microsoft Visual S
>     tudio/Common/MSDev98/Bin:/cygdrive/c/Program Files/Microsoft Visual =
>Studio/Commo
>     n/Tools:/cygdrive/c/Program Files/Microsoft Visual Studio/VC98/bin=20
>
>   (all that's really important is that the MinGW binaries come before =
>the cygwin binaries).
>
>   Then, I run a shell from cygwin (using the icon the cygwin install =
>leaves on the desktop, which gives me a terminal running bash), and do =
>the make from there.
>
>   But, my MINGW directory doesn't have "make.exe" in it.  There's a =
>mingw32-make.exe, but the purposely don't call it "make.exe", because it =
>sucks :)
>
>   I can't understand the particular error your make gave you, but I =
>don't know what file it's talking about.  (I think the note is that it's =
>trying to make gsm/src/add.o, which is should do from the implicit rule =
>from gsm/src/add.c).
>
>
>   So, I think the easiest way to get you going is to get yourself cygwin =
>(just run http://cygwin.com/setup.exe), find out what that make you're =
>using is and get rid of it, then build with cygwin's tools (except for =
>the compiler, for that use mingw).
>
>   The rest of your research, below, is unlikely to get you anywhere =
>helpful.  I don't maintain any of the other Makefiles other than =
>lib/Makefile simpleclient/testcall/Makefile and =
>simpleclient/wx/Makefile.  Even if those other Makefiles work, they'll =
>give you some library which isn't going to help you.
>
>
>   Also, please post to the mailing list; other people are working =
>through the same thing (]data[ from IRC, for example, just got a whole =
>"wx.exe" build going himself), and the discussion can either help =
>others, or perhaps others can help you.
>
>   -SteveK
>
>
>     Research:
>     went to iaxclient/lib/gsm/src: there is no add.o, just add.c
>     There is a "makefile" here, so I typed "make clean"; results: +ve
>     =20
>     Hacking: from iaxclient/lib/gsm, typed "make".  Results: +ve
>     Went back to iaxclient/lib typed: "make"
>     Resulting message:
>     The same but with code.o missing instead of add.o
>     =20
>     I will greatly appreciate your guidance through these difficulties.
>     =20
>     =20
>     Regards,
>     Uriel=20
>       -----Original Message-----
>       From: iax...@li... =
>[mailto:iax...@li...]On Behalf Of Steve =
>Kann
>       Sent: Wednesday, June 11, 2003 10:21 AM
>       To: ur...@ad...
>       Cc: iaxclient devel
>       Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin
>
>
>       Uriel,
>
>           There's three "maintained" makefiles within the project.  The =
>Makefile in iaxclient/lib, and the Makefiles in simpleclient/testcall =
>and simpleclient/wx.
>
>       Both of the simpleclient/*/Makefiles will call the Makefile in lib =
>to make the library, as both clients use the library, and thus require =
>the library (libiaxclient.a) to be built.
>
>       So, from clean CVS, you should be able to just go to =
>simpleclient/testcall, and type "make".
>
>       However, if you've tried other things, I'd say you'd be best off =
>going to iaxclient/lib, typing "make clean", then "make".  Then, go to =
>the client you want to make and type "make clean", "make".
>
>       (the client Makefiles won't "clean" the library).
>
>       First, try making "testcall", since for "wx", you'll also need to =
>have wxwindows installed, etc.  Definately a better first step is to =
>compile testcall.
>
>       And yes, there's no install targets in the Makefiles.  You don't =
>need to install the library, and the executable targets are standalone =
>(i.e. for wx, there's "wx.exe" for windows, "wx" for linux, and "wx.app" =
>for MacOSX).
>
>
>
>       On Wed, 2003-06-11 at 00:00, Uriel Carrasquilla wrote:=20
>         Steve:
>         I am having a hard time compiling with MinGW and Gygwin.
>         I downloaded the CVS from Monday night.
>         I went to the /iaxclient/simpleclient/wx  (where there is a =
>Makefile) and typed: make
>         Problems developed in the lib/gsm.  I can see in the wx/Makefile =
>that we are trying to make iaxclient.a from lib/gsm.  So I went over and =
>type
>         make iaxclient.a
>         could not find a file.  So I went to the gsm subdirectory and =
>somewhere in there there was another makefile (lower case which is =
>normally a second choice for make).  I did a make.
>         Went back one leve to lib/gsm and executed make=20
>         Got another file missing. =20
>         =20
>         My question: is there a sequence of "make" that I have to =
>execute?
>         what would it be?
>         I could not see and "install" in any of the Makefile.  is it by =
>design?
>         Regards,
>         Uriel=20
>           -----Original Message-----
>           From: iax...@li... =
>[mailto:iax...@li...]On Behalf Of Steve =
>Kann
>           Sent: Tuesday, June 10, 2003 7:48 PM
>           To: iaxclient devel
>           Subject: [Iaxclient-devel] some updates, and Ideas for =
>contributions..
>
>
>           1) (most relevant): put iax call processing (including audio) =
>into a separate thread.  This helps the most when you do things that =
>block the GUI thread, like resizing the window (Win32 only?).  And it =
>seems to also help the Mac a bit(*)
>
>           (*) The volume meters, implemented with progress bars via =
>wxwindows on the mac, eat a lot of CPU for their animation.  Not that it =
>doesn't look good.  I think that this caused some skips on the Mac.
>
>           2) Fixed the DTMF buttons that I broke sometime today or last =
>night.
>
>           3) Fixed PTT a bit.  (looking for feedback on how this works).
>
>           Also, due to a byproduct of the way I did things, if you =
>enable then disable PTT, you'll also be enabling silence =
>detection/suppression.  This will make the client not spit out any audio =
>frames until the input audio level reaches -40 DB. =20
>
>           There's been a lot of interest here on the list and on IRC =
>from a growing community.  That's cool.  People asked what they can help =
>with, so here's some ideas for adventurous souls:
>
>
>           1) IAX2:  You can build it via my Makefiles by setting =
>IAXVER=3D2 at the top of the =20
>                          library Makefile, or building the library by =
>running "make IAXVER=3D2".  It=20
>                          doesn't work quite right, though, so if someone =
>could try and figure that one=20
>                          out, it would be good.  Once it's working, IAX2 =
>should offer us a bunch of=20
>                          quality improvements, especially over the =
>internet.
>
>           2) Registration:  People out there want this, and it will make =
>the apps/library more    =20
>                          useful to the community.  Shouldn't be too =
>hard, but will need to be a bit    =20
>                          careful about keeping track of calls, sessions, =
>peers, etc.
>
>           3) A maintainer for VC++ Makefiles and/or .dsw files.  I don't =
>know this stuff, and I=20
>                         don't like tools you need your mouse for.  But, =
>if it helps people get more=20
>                         involved, I'm all for keeping a current .dsw/dsp =
>or whatever file in CVS, one=20
>                         for each of the Makefiles, I guess (lib, =
>testcall, wx).
>
>           4) Exposing Audio Settings:  Make controls (library functions =
>and GUI) for enumerating and choosing audio input/output devices.  This =
>may require either moving to the standard portaudio callback interface, =
>or hacking pablio to allow you to choose particular devices.  Also, =
>expose setting the input and output "levels".  It's probably best to =
>allow them to change this while the app is running, so you'll need to =
>close/re-open the audio device, etc.
>
>           5) MacOSX Mono audio problem:  Currently MacOSX audio comes =
>only out of the left channel.  Seems like a portaudio problem to track =
>down.
>
>           6) silence detection / dynamic range compression:  Figure out =
>good values or algorithms to make the client automatically (a) not send =
>any packets when there's no speech, (b) put out good consistent volume =
>when there is speech, even if people don't have consistent =
>microphone/soundcard settings, use laptop microphones or nice headsets.
>
>           7) Additional codec support:  I'd start with uLaw, to make =
>some #iaxclient user happy, but also because it's pretty easy to =
>implement, then also try iLBC and/or Speex.  Probably want one way for =
>the user to choose their preferred codec.
>
>           Hmm, that's a bunch of stuff :)
>
>           If anyone wants to step up for this stuff, let the list know, =
>so we all don't duplicate each other's work.
>
>
>           Happy IAX clienting!
>
>           -SteveK
>
>
>
>
>
>
>
>
>
>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."
>               =20
>
>
>
>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."
>           =20
>
>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."
>       =20
>
>
>
>
>------=_NextPart_000_00F2_01C3305D.39664000
>Content-Type: text/html;
>	charset="utf-8"
>Content-Transfer-Encoding: quoted-printable
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
><HTML><HEAD>
><META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
>charset=3Dutf-8">
>
>
><META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR></HEAD>
><BODY>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
>class=3D101360401-12062003>Steve:</SPAN></FONT></DIV>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
>class=3D101360401-12062003>you=20
>hit the nail on the head.&nbsp; I had renamed mingw make file to =
>make.&nbsp;=20
>This is because when I executed "make" from the bash shell interface it =
>could=20
>not find make.&nbsp; Let me try to figure out what I did wrong with my =
>Cygwin=20
>install.</SPAN></FONT></DIV>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
>class=3D101360401-12062003>Uriel</SPAN></FONT></DIV>
><BLOCKQUOTE>
>   <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
>face=3DTahoma=20
>   size=3D2>-----Original Message-----<BR><B>From:</B> Steve Kann=20
>   [mailto:st...@st...]<BR><B>Sent:</B> Wednesday, June 11, 2003 =
>7:34=20
>   PM<BR><B>To:</B> ur...@ad...<BR><B>Cc:</B> iaxclient=20
>   devel<BR><B>Subject:</B> RE: [Iaxclient-devel] Compiling with=20
>   MinGW/Cygwin<BR><BR></DIV></FONT>On Wed, 2003-06-11 at 19:55, Uriel=20
>   Carrasquilla wrote:=20
>   <BLOCKQUOTE TYPE=3D"CITE"><FONT size=3D2><I>Steve:<BR>My first step: =
>went to=20
>     ieaxclient/lib, typed: "make clean" <BR>Results: +ve<BR>My second =
>step: from=20
>     iaxclient/lib typed: "make"<BR>Resulting message:<BR>failed make =
>(e=3D2): the=20
>     system cannot find the file specified c"\MinGW\bin\make.exe ****=20
>     [gsm/src/add.o] Error 2</I></FONT> </BLOCKQUOTE><FONT =
>size=3D2><BR>hmm, OK, this=20
>   is interesting.&nbsp; <BR><BR>Your build environment is different from =
>mine,=20
>   in that you're using a "make" provided by MinGW, as opposed to the =
>cygwin=20
>   make.&nbsp; Their make might be broken in some way, although I think =
>someone=20
>   built sucessfully with MinGW with "msys" installed.<BR><BR>The way my=20
>   environment is set up, I have cygwin installed, and MinGW installed, =
>and then=20
>   I have the MinGW tools installed ahead of the cygwin stuff in my =
>path.&nbsp;=20
>   I.e. my path is:<BR><BR>
>   =
><BLOCKQUOTE>/cygdrive/c/MINGW/bin:/usr/local/bin:/usr/bin:/bin:/cygdrive/=
>c/SPRY/BIN:/cygdriv<BR>e/c/WINDOWS:/cygdrive/c/WINDOWS/system32:/cygdrive=
>/c/WINDOWS/system32/WBEM:/cygd<BR>rive/c/Program=20
>     Files/Real/Helix Producer Basic:/cygdrive/c/Program =
>Files/Microso<BR>ft=20
>     Visual Studio/Common/Tools/WinNT:/cygdrive/c/Program Files/Microsoft =
>Visual=20
>     S<BR>tudio/Common/MSDev98/Bin:/cygdrive/c/Program Files/Microsoft =
>Visual=20
>     Studio/Commo<BR>n/Tools:/cygdrive/c/Program Files/Microsoft Visual=20
>     Studio/VC98/bin </BLOCKQUOTE><BR>(all that's really important is =
>that the=20
>   MinGW binaries come before the cygwin binaries).<BR><BR>Then, I run a =
>shell=20
>   from cygwin (using the icon the cygwin install leaves on the desktop, =
>which=20
>   gives me a terminal running bash), and do the make from =
>there.<BR><BR>But, my=20
>   MINGW directory doesn't have "make.exe" in it.&nbsp; There's a=20
>   mingw32-make.exe, but the purposely don't call it "make.exe", because =
>it sucks=20
>   :)<BR><BR>I can't understand the particular error your make gave you, =
>but I=20
>   don't know what file it's talking about.&nbsp; (I think the note is =
>that it's=20
>   trying to make gsm/src/add.o, which is should do from the implicit =
>rule from=20
>   gsm/src/add.c).<BR><BR><BR>So, I think the easiest way to get you =
>going is to=20
>   get yourself cygwin (just run </FONT><A=20
>   href=3D"http://cygwin.com/setup.exe"><FONT=20
>   size=3D2>http://cygwin.com/setup.exe</FONT></A><FONT size=3D2>), find =
>out what=20
>   that make you're using is and get rid of it, then build with cygwin's =
>tools=20
>   (except for the compiler, for that use mingw).<BR><BR>The rest of your =
>
>   research, below, is unlikely to get you anywhere helpful.&nbsp; I =
>don't=20
>   maintain any of the other Makefiles other than lib/Makefile=20
>   simpleclient/testcall/Makefile and simpleclient/wx/Makefile.&nbsp; =
>Even if=20
>   those other Makefiles work, they'll give you some library which isn't =
>going to=20
>   help you.<BR><BR><BR>Also, please post to the mailing list; other =
>people are=20
>   working through the same thing (]data[ from IRC, for example, just got =
>a whole=20
>   "wx.exe" build going himself), and the discussion can either help =
>others, or=20
>   perhaps others can help you.<BR><BR>-SteveK<BR></FONT><BR>
>   <BLOCKQUOTE TYPE=3D"CITE"><FONT size=3D2><I>Research:<BR>went to=20
>     iaxclient/lib/gsm/src: there is no add.o, just add.c<BR>There is a=20
>     "makefile" here, so I typed "make clean"; results: =
>+ve</FONT><BR><FONT=20
>     color=3D#737373>&nbsp;</FONT><BR><FONT size=3D2>Hacking: from =
>iaxclient/lib/gsm,=20
>     typed "make".&nbsp; Results: +ve<BR>Went back to iaxclient/lib =
>typed:=20
>     "make"<BR>Resulting message:<BR>The same but with code.o missing =
>instead of=20
>     add.o</FONT><BR><FONT color=3D#737373>&nbsp;</FONT><BR><FONT =
>size=3D2>I will=20
>     greatly appreciate your guidance through these =
>difficulties.</FONT><BR><FONT=20
>     color=3D#737373>&nbsp;<BR>&nbsp;</FONT><BR><FONT=20
>     size=3D2>Regards,<BR>Uriel</FONT>=20
>     <BLOCKQUOTE><FONT color=3D#737373 size=3D2>-----Original=20
>       Message-----<BR><B>From:</B> =
>iax...@li...=20
>       [mailto:iax...@li...]<B>On Behalf =
>Of=20
>       </B>Steve Kann<BR><B>Sent:</B> Wednesday, June 11, 2003 10:21=20
>       AM<BR><B>To:</B> ur...@ad...<BR><B>Cc:</B> iaxclient=20
>       devel<BR><B>Subject:</B> RE: [Iaxclient-devel] Compiling with=20
>       MinGW/Cygwin<BR><BR></FONT><BR><FONT=20
>       color=3D#737373>Uriel,<BR><BR>&nbsp;&nbsp;&nbsp; There's three =
>"maintained"=20
>       makefiles within the project.&nbsp; The Makefile in iaxclient/lib, =
>and the=20
>       Makefiles in simpleclient/testcall and =
>simpleclient/wx.<BR><BR>Both of the=20
>       simpleclient/*/Makefiles will call the Makefile in lib to make the =
>
>       library, as both clients use the library, and thus require the =
>library=20
>       (libiaxclient.a) to be built.<BR><BR>So, from clean CVS, you =
>should be=20
>       able to just go to simpleclient/testcall, and type =
>"make".<BR><BR>However,=20
>       if you've tried other things, I'd say you'd be best off going to=20
>       iaxclient/lib, typing "make clean", then "make".&nbsp; Then, go to =
>the=20
>       client you want to make and type "make clean", "make".<BR><BR>(the =
>client=20
>       Makefiles won't "clean" the library).<BR><BR>First, try making =
>"testcall",=20
>       since for "wx", you'll also need to have wxwindows installed, =
>etc.&nbsp;=20
>       Definately a better first step is to compile testcall.<BR><BR>And =
>yes,=20
>       there's no install targets in the Makefiles.&nbsp; You don't need =
>to=20
>       install the library, and the executable targets are standalone =
>(i.e. for=20
>       wx, there's "wx.exe" for windows, "wx" for linux, and "wx.app" for =
>
>       MacOSX).<BR><BR><BR><BR>On Wed, 2003-06-11 at 00:00, Uriel =
>Carrasquilla=20
>       wrote: </FONT>
>       <BLOCKQUOTE TYPE=3D"CITE"><FONT color=3D#737373 =
>size=3D2>Steve:<BR>I am having=20
>         a hard time compiling with MinGW and Gygwin.<BR>I downloaded the =
>CVS=20
>         from Monday night.<BR>I went to the =
>/iaxclient/simpleclient/wx&nbsp;=20
>         (where there is a Makefile) and typed: make<BR>Problems =
>developed in the=20
>         lib/gsm.&nbsp; I can see in the wx/Makefile that we are trying =
>to make=20
>         iaxclient.a from lib/gsm.&nbsp; So I went over and type<BR>make=20
>         iaxclient.a<BR>could not find a file.&nbsp; So I went to the gsm =
>
>         subdirectory and somewhere in there there was another makefile =
>(lower=20
>         case which is normally a second choice for make).&nbsp; I did a=20
>         make.<BR>Went back one leve to lib/gsm and executed make <BR>Got =
>another=20
>         file missing.&nbsp; </FONT><BR><FONT=20
>         color=3D#737373>&nbsp;</FONT><BR><FONT color=3D#737373 =
>size=3D2>My question:=20
>         is there a sequence of "make" that I have to execute?<BR>what =
>would it=20
>         be?<BR>I could not see and "install" in any of the =
>Makefile.&nbsp; is it=20
>         by design?<BR>Regards,<BR>Uriel=20
>         <BLOCKQUOTE>-----Original Message-----<BR><B>From:</B>=20
>           iax...@li...=20
>           [mailto:iax...@li...]<B>On =
>Behalf Of=20
>           </B>Steve Kann<BR><B>Sent:</B> Tuesday, June 10, 2003 7:48=20
>           PM<BR><B>To:</B> iaxclient devel<BR><B>Subject:</B> =
>[Iaxclient-devel]=20
>           some updates, and Ideas for =
>contributions..<BR></FONT><BR><FONT=20
>           color=3D#737373><BR>1) (most relevant): put iax call =
>processing=20
>           (including audio) into a separate thread.&nbsp; This helps the =
>most=20
>           when you do things that block the GUI thread, like resizing =
>the window=20
>           (Win32 only?).&nbsp; And it seems to also help the Mac a=20
>           bit(*)<BR><BR>(*) The volume meters, implemented with progress =
>bars=20
>           via wxwindows on the mac, eat a lot of CPU for their =
>animation.&nbsp;=20
>           Not that it doesn't look good.&nbsp; I think that this caused =
>some=20
>           skips on the Mac.<BR><BR>2) Fixed the DTMF buttons that I =
>broke=20
>           sometime today or last night.<BR><BR>3) Fixed PTT a bit.&nbsp; =
>
>           (looking for feedback on how this works).<BR><BR>Also, due to =
>a=20
>           byproduct of the way I did things, if you enable then disable =
>PTT,=20
>           you'll also be enabling silence detection/suppression.&nbsp; =
>This will=20
>           make the client not spit out any audio frames until the input =
>audio=20
>           level reaches -40 DB.&nbsp; <BR><BR>There's been a lot of =
>interest=20
>           here on the list and on IRC from a growing community.&nbsp; =
>That's=20
>           cool.&nbsp; People asked what they can help with, so here's =
>some ideas=20
>           for adventurous souls:<BR><BR><BR>1) IAX2:&nbsp; You can build =
>it via=20
>           my Makefiles by setting IAXVER=3D2 at the top of the&nbsp;=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           library Makefile, or building the library by running "make=20
>           IAXVER=3D2".&nbsp; It=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           doesn't work quite right, though, so if someone could try and =
>figure=20
>           that one=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           out, it would be good.&nbsp; Once it's working, IAX2 should =
>offer us a=20
>           bunch of=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           quality improvements, especially over the internet.<BR><BR>2)=20
>           Registration:&nbsp; People out there want this, and it will =
>make the=20
>           apps/library more&nbsp;&nbsp;&nbsp;&nbsp;=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           useful to the community.&nbsp; Shouldn't be too hard, but will =
>need to=20
>           be a bit&nbsp;&nbsp;&nbsp;&nbsp;=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           careful about keeping track of calls, sessions, peers, =
>etc.<BR><BR>3)=20
>           A maintainer for VC++ Makefiles and/or .dsw files.&nbsp; I =
>don't know=20
>           this stuff, and I=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;=20
>           don't like tools you need your mouse for.&nbsp; But, if it =
>helps=20
>           people get more=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;=20
>           involved, I'm all for keeping a current .dsw/dsp or whatever =
>file in=20
>           CVS, one=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;=20
>           for each of the Makefiles, I guess (lib, testcall, =
>wx).<BR><BR>4)=20
>           Exposing Audio Settings:&nbsp; Make controls (library =
>functions and=20
>           GUI) for enumerating and choosing audio input/output =
>devices.&nbsp;=20
>           This may require either moving to the standard portaudio =
>callback=20
>           interface, or hacking pablio to allow you to choose particular =
>
>           devices.&nbsp; Also, expose setting the input and output=20
>           "levels".&nbsp; It's probably best to allow them to change =
>this while=20
>           the app is running, so you'll need to close/re-open the audio =
>device,=20
>           etc.<BR><BR>5) MacOSX Mono audio problem:&nbsp; Currently =
>MacOSX audio=20
>           comes only out of the left channel.&nbsp; Seems like a =
>portaudio=20
>           problem to track down.<BR><BR>6) silence detection / dynamic =
>range=20
>           compression:&nbsp; Figure out good values or algorithms to =
>make the=20
>           client automatically (a) not send any packets when there's no =
>speech,=20
>           (b) put out good consistent volume when there is speech, even =
>if=20
>           people don't have consistent microphone/soundcard settings, =
>use laptop=20
>           microphones or nice headsets.<BR><BR>7) Additional codec=20
>           support:&nbsp; I'd start with uLaw, to make some #iaxclient =
>user=20
>           happy, but also because it's pretty easy to implement, then =
>also try=20
>           iLBC and/or Speex.&nbsp; Probably want one way for the user to =
>choose=20
>           their preferred codec.<BR><BR>Hmm, that's a bunch of stuff=20
>           :)<BR><BR>If anyone wants to step up for this stuff, let the =
>list=20
>           know, so we all don't duplicate each other's =
>work.<BR><BR><BR>Happy=20
>           IAX =
>clienting!<BR><BR>-SteveK<BR><BR><BR><BR><BR></I></FONT><BR>
>           <TABLE cellPadding=3D0 cellSpacing=3D0 width=3D"100%">
>             <TBODY>
>             <TR></TR>
>             <TR></TR>
>             <TR></TR>
>             <TR></TR>
>             <TR>
>               <TD><PRE>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."</PRE></TD></TR></TBODY></TABLE></BLOCKQUOTE></BLOCKQUOTE>
>       <TABLE cellPadding=3D0 cellSpacing=3D0 width=3D"100%">
>         <TBODY>
>         <TR></TR>
>         <TR></TR>
>         <TR>
>           <TD><PRE>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."</PRE></TD></TR></TBODY></TABLE></BLOCKQUOTE></BLOCKQUOTE>
>   <TABLE cellPadding=3D0 cellSpacing=3D0 width=3D"100%">
>     <TBODY>
>     <TR>
>       <TD><PRE>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."</PRE></TD></TR></TBODY></TABLE><BR><FONT=20
>   color=3D#737373><I></I></FONT><BR></BLOCKQUOTE></BODY></HTML>
>
>------=_NextPart_000_00F2_01C3305D.39664000--
>
>
>
>
>--__--__--
>
>Message: 2
>Reply-To: <ur...@ad...>
>From: "Uriel Carrasquilla" <ur...@ad...>
>To: "'Steve Kann'" <st...@st...>
>Cc: "'iaxclient devel'" <iax...@li...>
>Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin
>Date: Wed, 11 Jun 2003 22:41:34 -0400
>
>This is a multi-part message in MIME format.
>
>------=_NextPart_000_00F8_01C3306A.9DF91800
>Content-Type: text/plain;
>	charset="utf-8"
>Content-Transfer-Encoding: quoted-printable
>
>Steve:
>It is now working with the "make" from Cygwin.  I had to download it =
>from http://cygwin.com/setup.exe as it is not part of the default =
>install.
>I was able to compile with "make clena" followed by "make" under =
>iaxclient/simpleclient/testcall.  It works and I tested it and modified =
>it to use my own *.  There was quite a bit of noise and quite a bit of =
>delay but it is very promissing.
>Then I got ambitious and tried the same steps undex =
>iaxclient/simpleclient/wx.  I watched in horror the screen go for quite =
>a while.  Then it stopped with a message "1 error in wx.o".  I tried to =
>redirect the output to file so I could attach it here but only got the =
>first few lines of the "Makefile" execution.  Then, when the Cygwin make =
>takes over, it all went back to the STD output, my screen.
>Since I made it this far, I am now more committed than ever.
>Did I miss a step to compile the "GUI" version?
>Regards,
>Uriel
>   -----Original Message-----
>   From: iax...@li... =
>[mailto:iax...@li...]On Behalf Of Steve =
>Kann
>   Sent: Wednesday, June 11, 2003 7:34 PM
>   To: ur...@ad...
>   Cc: iaxclient devel
>   Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin
>
>
>   On Wed, 2003-06-11 at 19:55, Uriel Carrasquilla wrote:=20
>     Steve:
>     My first step: went to ieaxclient/lib, typed: "make clean"=20
>     Results: +ve
>     My second step: from iaxclient/lib typed: "make"
>     Resulting message:
>     failed make (e=3D2): the system cannot find the file specified =
>c"\MinGW\bin\make.exe **** [gsm/src/add.o] Error 2=20
>
>   hmm, OK, this is interesting. =20
>
>   Your build environment is different from mine, in that you're using a =
>"make" provided by MinGW, as opposed to the cygwin make.  Their make =
>might be broken in some way, although I think someone built sucessfully =
>with MinGW with "msys" installed.
>
>   The way my environment is set up, I have cygwin installed, and MinGW =
>installed, and then I have the MinGW tools installed ahead of the cygwin =
>stuff in my path.  I.e. my path is:
>
>
>     =
>/cygdrive/c/MINGW/bin:/usr/local/bin:/usr/bin:/bin:/cygdrive/c/SPRY/BIN:/=
>cygdriv
>     =
>e/c/WINDOWS:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS/system32/WBE=
>M:/cygd
>     rive/c/Program Files/Real/Helix Producer Basic:/cygdrive/c/Program =
>Files/Microso
>     ft Visual Studio/Common/Tools/WinNT:/cygdrive/c/Program =
>Files/Microsoft Visual S
>     tudio/Common/MSDev98/Bin:/cygdrive/c/Program Files/Microsoft Visual =
>Studio/Commo
>     n/Tools:/cygdrive/c/Program Files/Microsoft Visual Studio/VC98/bin=20
>
>   (all that's really important is that the MinGW binaries come before =
>the cygwin binaries).
>
>   Then, I run a shell from cygwin (using the icon the cygwin install =
>leaves on the desktop, which gives me a terminal running bash), and do =
>the make from there.
>
>   But, my MINGW directory doesn't have "make.exe" in it.  There's a =
>mingw32-make.exe, but the purposely don't call it "make.exe", because it =
>sucks :)
>
>   I can't understand the particular error your make gave you, but I =
>don't know what file it's talking about.  (I think the note is that it's =
>trying to make gsm/src/add.o, which is should do from the implicit rule =
>from gsm/src/add.c).
>
>
>   So, I think the easiest way to get you going is to get yourself cygwin =
>(just run http://cygwin.com/setup.exe), find out what that make you're =
>using is and get rid of it, then build with cygwin's tools (except for =
>the compiler, for that use mingw).
>
>   The rest of your research, below, is unlikely to get you anywhere =
>helpful.  I don't maintain any of the other Makefiles other than =
>lib/Makefile simpleclient/testcall/Makefile and =
>simpleclient/wx/Makefile.  Even if those other Makefiles work, they'll =
>give you some library which isn't going to help you.
>
>
>   Also, please post to the mailing list; other people are working =
>through the same thing (]data[ from IRC, for example, just got a whole =
>"wx.exe" build going himself), and the discussion can either help =
>others, or perhaps others can help you.
>
>   -SteveK
>
>
>     Research:
>     went to iaxclient/lib/gsm/src: there is no add.o, just add.c
>     There is a "makefile" here, so I typed "make clean"; results: +ve
>     =20
>     Hacking: from iaxclient/lib/gsm, typed "make".  Results: +ve
>     Went back to iaxclient/lib typed: "make"
>     Resulting message:
>     The same but with code.o missing instead of add.o
>     =20
>     I will greatly appreciate your guidance through these difficulties.
>     =20
>     =20
>     Regards,
>     Uriel=20
>       -----Original Message-----
>       From: iax...@li... =
>[mailto:iax...@li...]On Behalf Of Steve =
>Kann
>       Sent: Wednesday, June 11, 2003 10:21 AM
>       To: ur...@ad...
>       Cc: iaxclient devel
>       Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin
>
>
>       Uriel,
>
>           There's three "maintained" makefiles within the project.  The =
>Makefile in iaxclient/lib, and the Makefiles in simpleclient/testcall =
>and simpleclient/wx.
>
>       Both of the simpleclient/*/Makefiles will call the Makefile in lib =
>to make the library, as both clients use the library, and thus require =
>the library (libiaxclient.a) to be built.
>
>       So, from clean CVS, you should be able to just go to =
>simpleclient/testcall, and type "make".
>
>       However, if you've tried other things, I'd say you'd be best off =
>going to iaxclient/lib, typing "make clean", then "make".  Then, go to =
>the client you want to make and type "make clean", "make".
>
>       (the client Makefiles won't "clean" the library).
>
>       First, try making "testcall", since for "wx", you'll also need to =
>have wxwindows installed, etc.  Definately a better first step is to =
>compile testcall.
>
>       And yes, there's no install targets in the Makefiles.  You don't =
>need to install the library, and the executable targets are standalone =
>(i.e. for wx, there's "wx.exe" for windows, "wx" for linux, and "wx.app" =
>for MacOSX).
>
>
>
>       On Wed, 2003-06-11 at 00:00, Uriel Carrasquilla wrote:=20
>         Steve:
>         I am having a hard time compiling with MinGW and Gygwin.
>         I downloaded the CVS from Monday night.
>         I went to the /iaxclient/simpleclient/wx  (where there is a =
>Makefile) and typed: make
>         Problems developed in the lib/gsm.  I can see in the wx/Makefile =
>that we are trying to make iaxclient.a from lib/gsm.  So I went over and =
>type
>         make iaxclient.a
>         could not find a file.  So I went to the gsm subdirectory and =
>somewhere in there there was another makefile (lower case which is =
>normally a second choice for make).  I did a make.
>         Went back one leve to lib/gsm and executed make=20
>         Got another file missing. =20
>         =20
>         My question: is there a sequence of "make" that I have to =
>execute?
>         what would it be?
>         I could not see and "install" in any of the Makefile.  is it by =
>design?
>         Regards,
>         Uriel=20
>           -----Original Message-----
>           From: iax...@li... =
>[mailto:iax...@li...]On Behalf Of Steve =
>Kann
>           Sent: Tuesday, June 10, 2003 7:48 PM
>           To: iaxclient devel
>           Subject: [Iaxclient-devel] some updates, and Ideas for =
>contributions..
>
>
>           1) (most relevant): put iax call processing (including audio) =
>into a separate thread.  This helps the most when you do things that =
>block the GUI thread, like resizing the window (Win32 only?).  And it =
>seems to also help the Mac a bit(*)
>
>           (*) The volume meters, implemented with progress bars via =
>wxwindows on the mac, eat a lot of CPU for their animation.  Not that it =
>doesn't look good.  I think that this caused some skips on the Mac.
>
>           2) Fixed the DTMF buttons that I broke sometime today or last =
>night.
>
>           3) Fixed PTT a bit.  (looking for feedback on how this works).
>
>           Also, due to a byproduct of the way I did things, if you =
>enable then disable PTT, you'll also be enabling silence =
>detection/suppression.  This will make the client not spit out any audio =
>frames until the input audio level reaches -40 DB. =20
>
>           There's been a lot of interest here on the list and on IRC =
>from a growing community.  That's cool.  People asked what they can help =
>with, so here's some ideas for adventurous souls:
>
>
>           1) IAX2:  You can build it via my Makefiles by setting =
>IAXVER=3D2 at the top of the =20
>                          library Makefile, or building the library by =
>running "make IAXVER=3D2".  It=20
>                          doesn't work quite right, though, so if someone =
>could try and figure that one=20
>                          out, it would be good.  Once it's working, IAX2 =
>should offer us a bunch of=20
>                          quality improvements, especially over the =
>internet.
>
>           2) Registration:  People out there want this, and it will make =
>the apps/library more    =20
>                          useful to the community.  Shouldn't be too =
>hard, but will need to be a bit    =20
>                          careful about keeping track of calls, sessions, =
>peers, etc.
>
>           3) A maintainer for VC++ Makefiles and/or .dsw files.  I don't =
>know this stuff, and I=20
>                         don't like tools you need your mouse for.  But, =
>if it helps people get more=20
>                         involved, I'm all for keeping a current .dsw/dsp =
>or whatever file in CVS, one=20
>                         for each of the Makefiles, I guess (lib, =
>testcall, wx).
>
>           4) Exposing Audio Settings:  Make controls (library functions =
>and GUI) for enumerating and choosing audio input/output devices.  This =
>may require either moving to the standard portaudio callback interface, =
>or hacking pablio to allow you to choose particular devices.  Also, =
>expose setting the input and output "levels".  It's probably best to =
>allow them to change this while the app is running, so you'll need to =
>close/re-open the audio device, etc.
>
>           5) MacOSX Mono audio problem:  Currently MacOSX audio comes =
>only out of the left channel.  Seems like a portaudio problem to track =
>down.
>
>           6) silence detection / dynamic range compression:  Figure out =
>good values or algorithms to make the client automatically (a) not send =
>any packets when there's no speech, (b) put out good consistent volume =
>when there is speech, even if people don't have consistent =
>microphone/soundcard settings, use laptop microphones or nice headsets.
>
>           7) Additional codec support:  I'd start with uLaw, to make =
>some #iaxclient user happy, but also because it's pretty easy to =
>implement, then also try iLBC and/or Speex.  Probably want one way for =
>the user to choose their preferred codec.
>
>           Hmm, that's a bunch of stuff :)
>
>           If anyone wants to step up for this stuff, let the list know, =
>so we all don't duplicate each other's work.
>
>
>           Happy IAX clienting!
>
>           -SteveK
>
>
>
>
>
>
>
>
>
>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."
>               =20
>
>
>
>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."
>           =20
>
>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."
>       =20
>
>
>
>
>------=_NextPart_000_00F8_01C3306A.9DF91800
>Content-Type: text/html;
>	charset="utf-8"
>Content-Transfer-Encoding: quoted-printable
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
><HTML><HEAD>
><META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
>charset=3Dutf-8">
>
>
><META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR></HEAD>
><BODY>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
>class=3D605463302-12062003>Steve:</SPAN></FONT></DIV>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
>class=3D605463302-12062003>It is=20
>now working with the "make" from Cygwin.&nbsp; I had to download it from =
><A=20
>href=3D"http://cygwin.com/setup.exe"><FONT=20
>size=3D2>http://cygwin.com/setup.exe</FONT></A> as it is not part of the =
>default=20
>install.</SPAN></FONT></DIV>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
>class=3D605463302-12062003>I was=20
>able to compile with "make clena" followed by "make" under=20
>iaxclient/simpleclient/testcall.&nbsp; It works and I tested it and =
>modified it=20
>to use my own *.&nbsp; There was quite a bit of noise and quite a bit of =
>delay=20
>but it is very promissing.</SPAN></FONT></DIV>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
>class=3D605463302-12062003>Then I=20
>got ambitious and tried the same steps undex =
>iaxclient/simpleclient/wx.&nbsp; I=20
>watched in horror the screen go for quite a while.&nbsp; Then it stopped =
>with a=20
>message "1 error in wx.o".&nbsp; I tried to redirect the output to file =
>so I=20
>could attach it here but only got the first few lines of the "Makefile"=20
>execution.&nbsp; Then, when the Cygwin make takes over, it all went back =
>to the=20
>STD output, my screen.</SPAN></FONT></DIV>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
>class=3D605463302-12062003>Since=20
>I made it this far, I am now more committed than =
>ever.</SPAN></FONT></DIV>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
>class=3D605463302-12062003>Did I=20
>miss a step to compile the "GUI" version?</SPAN></FONT></DIV>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
>class=3D605463302-12062003>Regards,</SPAN></FONT></DIV>
><DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
>class=3D605463302-12062003>Uriel</SPAN></FONT></DIV>
><BLOCKQUOTE>
>   <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
>face=3DTahoma=20
>   size=3D2>-----Original Message-----<BR><B>From:</B>=20
>   iax...@li...=20
>   [mailto:iax...@li...]<B>On Behalf Of =
></B>Steve=20
>   Kann<BR><B>Sent:</B> Wednesday, June 11, 2003 7:34 PM<BR><B>To:</B>=20
>   ur...@ad...<BR><B>Cc:</B> iaxclient devel<BR><B>Subject:</B> =
>RE:=20
>   [Iaxclient-devel] Compiling with MinGW/Cygwin<BR><BR></DIV></FONT>On =
>Wed,=20
>   2003-06-11 at 19:55, Uriel Carrasquilla wrote:=20
>   <BLOCKQUOTE TYPE=3D"CITE"><FONT size=3D2><I>Steve:<BR>My first step: =
>went to=20
>     ieaxclient/lib, typed: "make clean" <BR>Results: +ve<BR>My second =
>step: from=20
>     iaxclient/lib typed: "make"<BR>Resulting message:<BR>failed make =
>(e=3D2): the=20
>     system cannot find the file specified c"\MinGW\bin\make.exe ****=20
>     [gsm/src/add.o] Error 2</I></FONT> </BLOCKQUOTE><FONT =
>size=3D2><BR>hmm, OK, this=20
>   is interesting.&nbsp; <BR><BR>Your build environment is different from =
>mine,=20
>   in that you're using a "make" provided by MinGW, as opposed to the =
>cygwin=20
>   make.&nbsp; Their make might be broken in some way, although I think =
>someone=20
>   built sucessfully with MinGW with "msys" installed.<BR><BR>The way my=20
>   environment is set up, I have cygwin installed, and MinGW installed, =
>and then=20
>   I have the MinGW tools installed ahead of the cygwin stuff in my =
>path.&nbsp;=20
>   I.e. my path is:<BR><BR>
>   =
><BLOCKQUOTE>/cygdrive/c/MINGW/bin:/usr/local/bin:/usr/bin:/bin:/cygdrive/=
>c/SPRY/BIN:/cygdriv<BR>e/c/WINDOWS:/cygdrive/c/WINDOWS/system32:/cygdrive=
>/c/WINDOWS/system32/WBEM:/cygd<BR>rive/c/Program=20
>     Files/Real/Helix Producer Basic:/cygdrive/c/Program =
>Files/Microso<BR>ft=20
>     Visual Studio/Common/Tools/WinNT:/cygdrive/c/Program Files/Microsoft =
>Visual=20
>     S<BR>tudio/Common/MSDev98/Bin:/cygdrive/c/Program Files/Microsoft =
>Visual=20
>     Studio/Commo<BR>n/Tools:/cygdrive/c/Program Files/Microsoft Visual=20
>     Studio/VC98/bin </BLOCKQUOTE><BR>(all that's really important is =
>that the=20
>   MinGW binaries come before the cygwin binaries).<BR><BR>Then, I run a =
>shell=20
>   from cygwin (using the icon the cygwin install leaves on the desktop, =
>which=20
>   gives me a terminal running bash), and do the make from =
>there.<BR><BR>But, my=20
>   MINGW directory doesn't have "make.exe" in it.&nbsp; There's a=20
>   mingw32-make.exe, but the purposely don't call it "make.exe", because =
>it sucks=20
>   :)<BR><BR>I can't understand the particular error your make gave you, =
>but I=20
>   don't know what file it's talking about.&nbsp; (I think the note is =
>that it's=20
>   trying to make gsm/src/add.o, which is should do from the implicit =
>rule from=20
>   gsm/src/add.c).<BR><BR><BR>So, I think the easiest way to get you =
>going is to=20
>   get yourself cygwin (just run </FONT><A=20
>   href=3D"http://cygwin.com/setup.exe"><FONT=20
>   size=3D2>http://cygwin.com/setup.exe</FONT></A><FONT size=3D2>), find =
>out what=20
>   that make you're using is and get rid of it, then build with cygwin's =
>tools=20
>   (except for the compiler, for that use mingw).<BR><BR>The rest of your =
>
>   research, below, is unlikely to get you anywhere helpful.&nbsp; I =
>don't=20
>   maintain any of the other Makefiles other than lib/Makefile=20
>   simpleclient/testcall/Makefile and simpleclient/wx/Makefile.&nbsp; =
>Even if=20
>   those other Makefiles work, they'll give you some library which isn't =
>going to=20
>   help you.<BR><BR><BR>Also, please post to the mailing list; other =
>people are=20
>   working through the same thing (]data[ from IRC, for example, just got =
>a whole=20
>   "wx.exe" build going himself), and the discussion can either help =
>others, or=20
>   perhaps others can help you.<BR><BR>-SteveK<BR></FONT><BR>
>   <BLOCKQUOTE TYPE=3D"CITE"><FONT size=3D2><I>Research:<BR>went to=20
>     iaxclient/lib/gsm/src: there is no add.o, just add.c<BR>There is a=20
>     "makefile" here, so I typed "make clean"; results: =
>+ve</FONT><BR><FONT=20
>     color=3D#737373>&nbsp;</FONT><BR><FONT size=3D2>Hacking: from =
>iaxclient/lib/gsm,=20
>     typed "make".&nbsp; Results: +ve<BR>Went back to iaxclient/lib =
>typed:=20
>     "make"<BR>Resulting message:<BR>The same but with code.o missing =
>instead of=20
>     add.o</FONT><BR><FONT color=3D#737373>&nbsp;</FONT><BR><FONT =
>size=3D2>I will=20
>     greatly appreciate your guidance through these =
>difficulties.</FONT><BR><FONT=20
>     color=3D#737373>&nbsp;<BR>&nbsp;</FONT><BR><FONT=20
>     size=3D2>Regards,<BR>Uriel</FONT>=20
>     <BLOCKQUOTE><FONT color=3D#737373 size=3D2>-----Original=20
>       Message-----<BR><B>From:</B> =
>iax...@li...=20
>       [mailto:iax...@li...]<B>On Behalf =
>Of=20
>       </B>Steve Kann<BR><B>Sent:</B> Wednesday, June 11, 2003 10:21=20
>       AM<BR><B>To:</B> ur...@ad...<BR><B>Cc:</B> iaxclient=20
>       devel<BR><B>Subject:</B> RE: [Iaxclient-devel] Compiling with=20
>       MinGW/Cygwin<BR><BR></FONT><BR><FONT=20
>       color=3D#737373>Uriel,<BR><BR>&nbsp;&nbsp;&nbsp; There's three =
>"maintained"=20
>       makefiles within the project.&nbsp; The Makefile in iaxclient/lib, =
>and the=20
>       Makefiles in simpleclient/testcall and =
>simpleclient/wx.<BR><BR>Both of the=20
>       simpleclient/*/Makefiles will call the Makefile in lib to make the =
>
>       library, as both clients use the library, and thus require the =
>library=20
>       (libiaxclient.a) to be built.<BR><BR>So, from clean CVS, you =
>should be=20
>       able to just go to simpleclient/testcall, and type =
>"make".<BR><BR>However,=20
>       if you've tried other things, I'd say you'd be best off going to=20
>       iaxclient/lib, typing "make clean", then "make".&nbsp; Then, go to =
>the=20
>       client you want to make and type "make clean", "make".<BR><BR>(the =
>client=20
>       Makefiles won't "clean" the library).<BR><BR>First, try making =
>"testcall",=20
>       since for "wx", you'll also need to have wxwindows installed, =
>etc.&nbsp;=20
>       Definately a better first step is to compile testcall.<BR><BR>And =
>yes,=20
>       there's no install targets in the Makefiles.&nbsp; You don't need =
>to=20
>       install the library, and the executable targets are standalone =
>(i.e. for=20
>       wx, there's "wx.exe" for windows, "wx" for linux, and "wx.app" for =
>
>       MacOSX).<BR><BR><BR><BR>On Wed, 2003-06-11 at 00:00, Uriel =
>Carrasquilla=20
>       wrote: </FONT>
>       <BLOCKQUOTE TYPE=3D"CITE"><FONT color=3D#737373 =
>size=3D2>Steve:<BR>I am having=20
>         a hard time compiling with MinGW and Gygwin.<BR>I downloaded the =
>CVS=20
>         from Monday night.<BR>I went to the =
>/iaxclient/simpleclient/wx&nbsp;=20
>         (where there is a Makefile) and typed: make<BR>Problems =
>developed in the=20
>         lib/gsm.&nbsp; I can see in the wx/Makefile that we are trying =
>to make=20
>         iaxclient.a from lib/gsm.&nbsp; So I went over and type<BR>make=20
>         iaxclient.a<BR>could not find a file.&nbsp; So I went to the gsm =
>
>         subdirectory and somewhere in there there was another makefile =
>(lower=20
>         case which is normally a second choice for make).&nbsp; I did a=20
>         make.<BR>Went back one leve to lib/gsm and executed make <BR>Got =
>another=20
>         file missing.&nbsp; </FONT><BR><FONT=20
>         color=3D#737373>&nbsp;</FONT><BR><FONT color=3D#737373 =
>size=3D2>My question:=20
>         is there a sequence of "make" that I have to execute?<BR>what =
>would it=20
>         be?<BR>I could not see and "install" in any of the =
>Makefile.&nbsp; is it=20
>         by design?<BR>Regards,<BR>Uriel=20
>         <BLOCKQUOTE>-----Original Message-----<BR><B>From:</B>=20
>           iax...@li...=20
>           [mailto:iax...@li...]<B>On =
>Behalf Of=20
>           </B>Steve Kann<BR><B>Sent:</B> Tuesday, June 10, 2003 7:48=20
>           PM<BR><B>To:</B> iaxclient devel<BR><B>Subject:</B> =
>[Iaxclient-devel]=20
>           some updates, and Ideas for =
>contributions..<BR></FONT><BR><FONT=20
>           color=3D#737373><BR>1) (most relevant): put iax call =
>processing=20
>           (including audio) into a separate thread.&nbsp; This helps the =
>most=20
>           when you do things that block the GUI thread, like resizing =
>the window=20
>           (Win32 only?).&nbsp; And it seems to also help the Mac a=20
>           bit(*)<BR><BR>(*) The volume meters, implemented with progress =
>bars=20
>           via wxwindows on the mac, eat a lot of CPU for their =
>animation.&nbsp;=20
>           Not that it doesn't look good.&nbsp; I think that this caused =
>some=20
>           skips on the Mac.<BR><BR>2) Fixed the DTMF buttons that I =
>broke=20
>           sometime today or last night.<BR><BR>3) Fixed PTT a bit.&nbsp; =
>
>           (looking for feedback on how this works).<BR><BR>Also, due to =
>a=20
>           byproduct of the way I did things, if you enable then disable =
>PTT,=20
>           you'll also be enabling silence detection/suppression.&nbsp; =
>This will=20
>           make the client not spit out any audio frames until the input =
>audio=20
>           level reaches -40 DB.&nbsp; <BR><BR>There's been a lot of =
>interest=20
>           here on the list and on IRC from a growing community.&nbsp; =
>That's=20
>           cool.&nbsp; People asked what they can help with, so here's =
>some ideas=20
>           for adventurous souls:<BR><BR><BR>1) IAX2:&nbsp; You can build =
>it via=20
>           my Makefiles by setting IAXVER=3D2 at the top of the&nbsp;=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           library Makefile, or building the library by running "make=20
>           IAXVER=3D2".&nbsp; It=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           doesn't work quite right, though, so if someone could try and =
>figure=20
>           that one=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           out, it would be good.&nbsp; Once it's working, IAX2 should =
>offer us a=20
>           bunch of=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           quality improvements, especially over the internet.<BR><BR>2)=20
>           Registration:&nbsp; People out there want this, and it will =
>make the=20
>           apps/library more&nbsp;&nbsp;&nbsp;&nbsp;=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           useful to the community.&nbsp; Shouldn't be too hard, but will =
>need to=20
>           be a bit&nbsp;&nbsp;&nbsp;&nbsp;=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;&nbsp;=20
>           careful about keeping track of calls, sessions, peers, =
>etc.<BR><BR>3)=20
>           A maintainer for VC++ Makefiles and/or .dsw files.&nbsp; I =
>don't know=20
>           this stuff, and I=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;=20
>           don't like tools you need your mouse for.&nbsp; But, if it =
>helps=20
>           people get more=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;=20
>           involved, I'm all for keeping a current .dsw/dsp or whatever =
>file in=20
>           CVS, one=20
>           =
><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
>sp;&nbsp;=20
>           for each of the Makefiles, I guess (lib, testcall, =
>wx).<BR><BR>4)=20
>           Exposing Audio Settings:&nbsp; Make controls (library =
>functions and=20
>           GUI) for enumerating and choosing audio input/output =
>devices.&nbsp;=20
>           This may require either moving to the standard portaudio =
>callback=20
>           interface, or hacking pablio to allow you to choose particular =
>
>           devices.&nbsp; Also, expose setting the input and output=20
>           "levels".&nbsp; It's probably best to allow them to change =
>this while=20
>           the app is running, so you'll need to close/re-open the audio =
>device,=20
>           etc.<BR><BR>5) MacOSX Mono audio problem:&nbsp; Currently =
>MacOSX audio=20
>           comes only out of the left channel.&nbsp; Seems like a =
>portaudio=20
>           problem to track down.<BR><BR>6) silence detection / dynamic =
>range=20
>           compression:&nbsp; Figure out good values or algorithms to =
>make the=20
>           client automatically (a) not send any packets when there's no =
>speech,=20
>           (b) put out good consistent volume when there is speech, even =
>if=20
>           people don't have consistent microphone/soundcard settings, =
>use laptop=20
>           microphones or nice headsets.<BR><BR>7) Additional codec=20
>           support:&nbsp; I'd start with uLaw, to make some #iaxclient =
>user=20
>           happy, but also because it's pretty easy to implement, then =
>also try=20
>           iLBC and/or Speex.&nbsp; Probably want one way for the user to =
>choose=20
>           their preferred codec.<BR><BR>Hmm, that's a bunch of stuff=20
>           :)<BR><BR>If anyone wants to step up for this stuff, let the =
>list=20
>           know, so we all don't duplicate each other's =
>work.<BR><BR><BR>Happy=20
>           IAX =
>clienting!<BR><BR>-SteveK<BR><BR><BR><BR><BR></I></FONT><BR>
>           <TABLE cellPadding=3D0 cellSpacing=3D0 width=3D"100%">
>             <TBODY>
>             <TR></TR>
>             <TR></TR>
>             <TR></TR>
>             <TR></TR>
>             <TR>
>               <TD><PRE>--=20
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed =
>Linux."</PRE></TD></TR></TBODY></TABLE></BLOCKQUOTE></BLOCKQUOTE>
>       <TABLE cellPadding=3D0 cellSpacing=3D0 width=3D"100%">
>         <TBODY>
>   ...
 
[truncated message content]

RE: [Iaxclient-devel] Compiling with MinGW/Cygwin

[Uriel C. <ur...@ad...>]

Steve:
It is now working with the "make" from Cygwin.  I had to download it =
from http://cygwin.com/setup.exe as it is not part of the default =
install.
I was able to compile with "make clena" followed by "make" under =
iaxclient/simpleclient/testcall.  It works and I tested it and modified =
it to use my own *.  There was quite a bit of noise and quite a bit of =
delay but it is very promissing.
Then I got ambitious and tried the same steps undex =
iaxclient/simpleclient/wx.  I watched in horror the screen go for quite =
a while.  Then it stopped with a message "1 error in wx.o".  I tried to =
redirect the output to file so I could attach it here but only got the =
first few lines of the "Makefile" execution.  Then, when the Cygwin make =
takes over, it all went back to the STD output, my screen.
Since I made it this far, I am now more committed than ever.
Did I miss a step to compile the "GUI" version?
Regards,
Uriel
  -----Original Message-----
  From: iax...@li... =
[mailto:iax...@li...]On Behalf Of Steve =
Kann
  Sent: Wednesday, June 11, 2003 7:34 PM
  To: ur...@ad...
  Cc: iaxclient devel
  Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin


  On Wed, 2003-06-11 at 19:55, Uriel Carrasquilla wrote:=20
    Steve:
    My first step: went to ieaxclient/lib, typed: "make clean"=20
    Results: +ve
    My second step: from iaxclient/lib typed: "make"
    Resulting message:
    failed make (e=3D2): the system cannot find the file specified =
c"\MinGW\bin\make.exe **** [gsm/src/add.o] Error 2=20

  hmm, OK, this is interesting. =20

  Your build environment is different from mine, in that you're using a =
"make" provided by MinGW, as opposed to the cygwin make.  Their make =
might be broken in some way, although I think someone built sucessfully =
with MinGW with "msys" installed.

  The way my environment is set up, I have cygwin installed, and MinGW =
installed, and then I have the MinGW tools installed ahead of the cygwin =
stuff in my path.  I.e. my path is:


    =
/cygdrive/c/MINGW/bin:/usr/local/bin:/usr/bin:/bin:/cygdrive/c/SPRY/BIN:/=
cygdriv
    =
e/c/WINDOWS:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS/system32/WBE=
M:/cygd
    rive/c/Program Files/Real/Helix Producer Basic:/cygdrive/c/Program =
Files/Microso
    ft Visual Studio/Common/Tools/WinNT:/cygdrive/c/Program =
Files/Microsoft Visual S
    tudio/Common/MSDev98/Bin:/cygdrive/c/Program Files/Microsoft Visual =
Studio/Commo
    n/Tools:/cygdrive/c/Program Files/Microsoft Visual Studio/VC98/bin=20

  (all that's really important is that the MinGW binaries come before =
the cygwin binaries).

  Then, I run a shell from cygwin (using the icon the cygwin install =
leaves on the desktop, which gives me a terminal running bash), and do =
the make from there.

  But, my MINGW directory doesn't have "make.exe" in it.  There's a =
mingw32-make.exe, but the purposely don't call it "make.exe", because it =
sucks :)

  I can't understand the particular error your make gave you, but I =
don't know what file it's talking about.  (I think the note is that it's =
trying to make gsm/src/add.o, which is should do from the implicit rule =
from gsm/src/add.c).


  So, I think the easiest way to get you going is to get yourself cygwin =
(just run http://cygwin.com/setup.exe), find out what that make you're =
using is and get rid of it, then build with cygwin's tools (except for =
the compiler, for that use mingw).

  The rest of your research, below, is unlikely to get you anywhere =
helpful.  I don't maintain any of the other Makefiles other than =
lib/Makefile simpleclient/testcall/Makefile and =
simpleclient/wx/Makefile.  Even if those other Makefiles work, they'll =
give you some library which isn't going to help you.


  Also, please post to the mailing list; other people are working =
through the same thing (]data[ from IRC, for example, just got a whole =
"wx.exe" build going himself), and the discussion can either help =
others, or perhaps others can help you.

  -SteveK


    Research:
    went to iaxclient/lib/gsm/src: there is no add.o, just add.c
    There is a "makefile" here, so I typed "make clean"; results: +ve
    =20
    Hacking: from iaxclient/lib/gsm, typed "make".  Results: +ve
    Went back to iaxclient/lib typed: "make"
    Resulting message:
    The same but with code.o missing instead of add.o
    =20
    I will greatly appreciate your guidance through these difficulties.
    =20
    =20
    Regards,
    Uriel=20
      -----Original Message-----
      From: iax...@li... =
[mailto:iax...@li...]On Behalf Of Steve =
Kann
      Sent: Wednesday, June 11, 2003 10:21 AM
      To: ur...@ad...
      Cc: iaxclient devel
      Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin


      Uriel,

          There's three "maintained" makefiles within the project.  The =
Makefile in iaxclient/lib, and the Makefiles in simpleclient/testcall =
and simpleclient/wx.

      Both of the simpleclient/*/Makefiles will call the Makefile in lib =
to make the library, as both clients use the library, and thus require =
the library (libiaxclient.a) to be built.

      So, from clean CVS, you should be able to just go to =
simpleclient/testcall, and type "make".

      However, if you've tried other things, I'd say you'd be best off =
going to iaxclient/lib, typing "make clean", then "make".  Then, go to =
the client you want to make and type "make clean", "make".

      (the client Makefiles won't "clean" the library).

      First, try making "testcall", since for "wx", you'll also need to =
have wxwindows installed, etc.  Definately a better first step is to =
compile testcall.

      And yes, there's no install targets in the Makefiles.  You don't =
need to install the library, and the executable targets are standalone =
(i.e. for wx, there's "wx.exe" for windows, "wx" for linux, and "wx.app" =
for MacOSX).



      On Wed, 2003-06-11 at 00:00, Uriel Carrasquilla wrote:=20
        Steve:
        I am having a hard time compiling with MinGW and Gygwin.
        I downloaded the CVS from Monday night.
        I went to the /iaxclient/simpleclient/wx  (where there is a =
Makefile) and typed: make
        Problems developed in the lib/gsm.  I can see in the wx/Makefile =
that we are trying to make iaxclient.a from lib/gsm.  So I went over and =
type
        make iaxclient.a
        could not find a file.  So I went to the gsm subdirectory and =
somewhere in there there was another makefile (lower case which is =
normally a second choice for make).  I did a make.
        Went back one leve to lib/gsm and executed make=20
        Got another file missing. =20
        =20
        My question: is there a sequence of "make" that I have to =
execute?
        what would it be?
        I could not see and "install" in any of the Makefile.  is it by =
design?
        Regards,
        Uriel=20
          -----Original Message-----
          From: iax...@li... =
[mailto:iax...@li...]On Behalf Of Steve =
Kann
          Sent: Tuesday, June 10, 2003 7:48 PM
          To: iaxclient devel
          Subject: [Iaxclient-devel] some updates, and Ideas for =
contributions..


          1) (most relevant): put iax call processing (including audio) =
into a separate thread.  This helps the most when you do things that =
block the GUI thread, like resizing the window (Win32 only?).  And it =
seems to also help the Mac a bit(*)

          (*) The volume meters, implemented with progress bars via =
wxwindows on the mac, eat a lot of CPU for their animation.  Not that it =
doesn't look good.  I think that this caused some skips on the Mac.

          2) Fixed the DTMF buttons that I broke sometime today or last =
night.

          3) Fixed PTT a bit.  (looking for feedback on how this works).

          Also, due to a byproduct of the way I did things, if you =
enable then disable PTT, you'll also be enabling silence =
detection/suppression.  This will make the client not spit out any audio =
frames until the input audio level reaches -40 DB. =20

          There's been a lot of interest here on the list and on IRC =
from a growing community.  That's cool.  People asked what they can help =
with, so here's some ideas for adventurous souls:


          1) IAX2:  You can build it via my Makefiles by setting =
IAXVER=3D2 at the top of the =20
                         library Makefile, or building the library by =
running "make IAXVER=3D2".  It=20
                         doesn't work quite right, though, so if someone =
could try and figure that one=20
                         out, it would be good.  Once it's working, IAX2 =
should offer us a bunch of=20
                         quality improvements, especially over the =
internet.

          2) Registration:  People out there want this, and it will make =
the apps/library more    =20
                         useful to the community.  Shouldn't be too =
hard, but will need to be a bit    =20
                         careful about keeping track of calls, sessions, =
peers, etc.

          3) A maintainer for VC++ Makefiles and/or .dsw files.  I don't =
know this stuff, and I=20
                        don't like tools you need your mouse for.  But, =
if it helps people get more=20
                        involved, I'm all for keeping a current .dsw/dsp =
or whatever file in CVS, one=20
                        for each of the Makefiles, I guess (lib, =
testcall, wx).

          4) Exposing Audio Settings:  Make controls (library functions =
and GUI) for enumerating and choosing audio input/output devices.  This =
may require either moving to the standard portaudio callback interface, =
or hacking pablio to allow you to choose particular devices.  Also, =
expose setting the input and output "levels".  It's probably best to =
allow them to change this while the app is running, so you'll need to =
close/re-open the audio device, etc.

          5) MacOSX Mono audio problem:  Currently MacOSX audio comes =
only out of the left channel.  Seems like a portaudio problem to track =
down.

          6) silence detection / dynamic range compression:  Figure out =
good values or algorithms to make the client automatically (a) not send =
any packets when there's no speech, (b) put out good consistent volume =
when there is speech, even if people don't have consistent =
microphone/soundcard settings, use laptop microphones or nice headsets.

          7) Additional codec support:  I'd start with uLaw, to make =
some #iaxclient user happy, but also because it's pretty easy to =
implement, then also try iLBC and/or Speex.  Probably want one way for =
the user to choose their preferred codec.

          Hmm, that's a bunch of stuff :)

          If anyone wants to step up for this stuff, let the list know, =
so we all don't duplicate each other's work.


          Happy IAX clienting!

          -SteveK









--=20
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed =
Linux."
              =20



--=20
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed =
Linux."
          =20

--=20
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed =
Linux."
      =20

RE: [Iaxclient-devel] Compiling with MinGW/Cygwin

[Uriel C. <ur...@ad...>]

Steve:
you hit the nail on the head.  I had renamed mingw make file to make.  =
This is because when I executed "make" from the bash shell interface it =
could not find make.  Let me try to figure out what I did wrong with my =
Cygwin install.
Uriel
  -----Original Message-----
  From: Steve Kann [mailto:st...@st...]
  Sent: Wednesday, June 11, 2003 7:34 PM
  To: ur...@ad...
  Cc: iaxclient devel
  Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin


  On Wed, 2003-06-11 at 19:55, Uriel Carrasquilla wrote:=20
    Steve:
    My first step: went to ieaxclient/lib, typed: "make clean"=20
    Results: +ve
    My second step: from iaxclient/lib typed: "make"
    Resulting message:
    failed make (e=3D2): the system cannot find the file specified =
c"\MinGW\bin\make.exe **** [gsm/src/add.o] Error 2=20

  hmm, OK, this is interesting. =20

  Your build environment is different from mine, in that you're using a =
"make" provided by MinGW, as opposed to the cygwin make.  Their make =
might be broken in some way, although I think someone built sucessfully =
with MinGW with "msys" installed.

  The way my environment is set up, I have cygwin installed, and MinGW =
installed, and then I have the MinGW tools installed ahead of the cygwin =
stuff in my path.  I.e. my path is:


    =
/cygdrive/c/MINGW/bin:/usr/local/bin:/usr/bin:/bin:/cygdrive/c/SPRY/BIN:/=
cygdriv
    =
e/c/WINDOWS:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS/system32/WBE=
M:/cygd
    rive/c/Program Files/Real/Helix Producer Basic:/cygdrive/c/Program =
Files/Microso
    ft Visual Studio/Common/Tools/WinNT:/cygdrive/c/Program =
Files/Microsoft Visual S
    tudio/Common/MSDev98/Bin:/cygdrive/c/Program Files/Microsoft Visual =
Studio/Commo
    n/Tools:/cygdrive/c/Program Files/Microsoft Visual Studio/VC98/bin=20

  (all that's really important is that the MinGW binaries come before =
the cygwin binaries).

  Then, I run a shell from cygwin (using the icon the cygwin install =
leaves on the desktop, which gives me a terminal running bash), and do =
the make from there.

  But, my MINGW directory doesn't have "make.exe" in it.  There's a =
mingw32-make.exe, but the purposely don't call it "make.exe", because it =
sucks :)

  I can't understand the particular error your make gave you, but I =
don't know what file it's talking about.  (I think the note is that it's =
trying to make gsm/src/add.o, which is should do from the implicit rule =
from gsm/src/add.c).


  So, I think the easiest way to get you going is to get yourself cygwin =
(just run http://cygwin.com/setup.exe), find out what that make you're =
using is and get rid of it, then build with cygwin's tools (except for =
the compiler, for that use mingw).

  The rest of your research, below, is unlikely to get you anywhere =
helpful.  I don't maintain any of the other Makefiles other than =
lib/Makefile simpleclient/testcall/Makefile and =
simpleclient/wx/Makefile.  Even if those other Makefiles work, they'll =
give you some library which isn't going to help you.


  Also, please post to the mailing list; other people are working =
through the same thing (]data[ from IRC, for example, just got a whole =
"wx.exe" build going himself), and the discussion can either help =
others, or perhaps others can help you.

  -SteveK


    Research:
    went to iaxclient/lib/gsm/src: there is no add.o, just add.c
    There is a "makefile" here, so I typed "make clean"; results: +ve
    =20
    Hacking: from iaxclient/lib/gsm, typed "make".  Results: +ve
    Went back to iaxclient/lib typed: "make"
    Resulting message:
    The same but with code.o missing instead of add.o
    =20
    I will greatly appreciate your guidance through these difficulties.
    =20
    =20
    Regards,
    Uriel=20
      -----Original Message-----
      From: iax...@li... =
[mailto:iax...@li...]On Behalf Of Steve =
Kann
      Sent: Wednesday, June 11, 2003 10:21 AM
      To: ur...@ad...
      Cc: iaxclient devel
      Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin


      Uriel,

          There's three "maintained" makefiles within the project.  The =
Makefile in iaxclient/lib, and the Makefiles in simpleclient/testcall =
and simpleclient/wx.

      Both of the simpleclient/*/Makefiles will call the Makefile in lib =
to make the library, as both clients use the library, and thus require =
the library (libiaxclient.a) to be built.

      So, from clean CVS, you should be able to just go to =
simpleclient/testcall, and type "make".

      However, if you've tried other things, I'd say you'd be best off =
going to iaxclient/lib, typing "make clean", then "make".  Then, go to =
the client you want to make and type "make clean", "make".

      (the client Makefiles won't "clean" the library).

      First, try making "testcall", since for "wx", you'll also need to =
have wxwindows installed, etc.  Definately a better first step is to =
compile testcall.

      And yes, there's no install targets in the Makefiles.  You don't =
need to install the library, and the executable targets are standalone =
(i.e. for wx, there's "wx.exe" for windows, "wx" for linux, and "wx.app" =
for MacOSX).



      On Wed, 2003-06-11 at 00:00, Uriel Carrasquilla wrote:=20
        Steve:
        I am having a hard time compiling with MinGW and Gygwin.
        I downloaded the CVS from Monday night.
        I went to the /iaxclient/simpleclient/wx  (where there is a =
Makefile) and typed: make
        Problems developed in the lib/gsm.  I can see in the wx/Makefile =
that we are trying to make iaxclient.a from lib/gsm.  So I went over and =
type
        make iaxclient.a
        could not find a file.  So I went to the gsm subdirectory and =
somewhere in there there was another makefile (lower case which is =
normally a second choice for make).  I did a make.
        Went back one leve to lib/gsm and executed make=20
        Got another file missing. =20
        =20
        My question: is there a sequence of "make" that I have to =
execute?
        what would it be?
        I could not see and "install" in any of the Makefile.  is it by =
design?
        Regards,
        Uriel=20
          -----Original Message-----
          From: iax...@li... =
[mailto:iax...@li...]On Behalf Of Steve =
Kann
          Sent: Tuesday, June 10, 2003 7:48 PM
          To: iaxclient devel
          Subject: [Iaxclient-devel] some updates, and Ideas for =
contributions..


          1) (most relevant): put iax call processing (including audio) =
into a separate thread.  This helps the most when you do things that =
block the GUI thread, like resizing the window (Win32 only?).  And it =
seems to also help the Mac a bit(*)

          (*) The volume meters, implemented with progress bars via =
wxwindows on the mac, eat a lot of CPU for their animation.  Not that it =
doesn't look good.  I think that this caused some skips on the Mac.

          2) Fixed the DTMF buttons that I broke sometime today or last =
night.

          3) Fixed PTT a bit.  (looking for feedback on how this works).

          Also, due to a byproduct of the way I did things, if you =
enable then disable PTT, you'll also be enabling silence =
detection/suppression.  This will make the client not spit out any audio =
frames until the input audio level reaches -40 DB. =20

          There's been a lot of interest here on the list and on IRC =
from a growing community.  That's cool.  People asked what they can help =
with, so here's some ideas for adventurous souls:


          1) IAX2:  You can build it via my Makefiles by setting =
IAXVER=3D2 at the top of the =20
                         library Makefile, or building the library by =
running "make IAXVER=3D2".  It=20
                         doesn't work quite right, though, so if someone =
could try and figure that one=20
                         out, it would be good.  Once it's working, IAX2 =
should offer us a bunch of=20
                         quality improvements, especially over the =
internet.

          2) Registration:  People out there want this, and it will make =
the apps/library more    =20
                         useful to the community.  Shouldn't be too =
hard, but will need to be a bit    =20
                         careful about keeping track of calls, sessions, =
peers, etc.

          3) A maintainer for VC++ Makefiles and/or .dsw files.  I don't =
know this stuff, and I=20
                        don't like tools you need your mouse for.  But, =
if it helps people get more=20
                        involved, I'm all for keeping a current .dsw/dsp =
or whatever file in CVS, one=20
                        for each of the Makefiles, I guess (lib, =
testcall, wx).

          4) Exposing Audio Settings:  Make controls (library functions =
and GUI) for enumerating and choosing audio input/output devices.  This =
may require either moving to the standard portaudio callback interface, =
or hacking pablio to allow you to choose particular devices.  Also, =
expose setting the input and output "levels".  It's probably best to =
allow them to change this while the app is running, so you'll need to =
close/re-open the audio device, etc.

          5) MacOSX Mono audio problem:  Currently MacOSX audio comes =
only out of the left channel.  Seems like a portaudio problem to track =
down.

          6) silence detection / dynamic range compression:  Figure out =
good values or algorithms to make the client automatically (a) not send =
any packets when there's no speech, (b) put out good consistent volume =
when there is speech, even if people don't have consistent =
microphone/soundcard settings, use laptop microphones or nice headsets.

          7) Additional codec support:  I'd start with uLaw, to make =
some #iaxclient user happy, but also because it's pretty easy to =
implement, then also try iLBC and/or Speex.  Probably want one way for =
the user to choose their preferred codec.

          Hmm, that's a bunch of stuff :)

          If anyone wants to step up for this stuff, let the list know, =
so we all don't duplicate each other's work.


          Happy IAX clienting!

          -SteveK









--=20
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed =
Linux."
              =20



--=20
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed =
Linux."
          =20

--=20
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed =
Linux."
      =20

RE: [Iaxclient-devel] Compiling with MinGW/Cygwin

[Steve K. <st...@st...>]

On Wed, 2003-06-11 at 19:55, Uriel Carrasquilla wrote:

> Steve:
> My first step: went to ieaxclient/lib, typed: "make clean" 
> Results: +ve
> My second step: from iaxclient/lib typed: "make"
> Resulting message:
> failed make (e=2): the system cannot find the file specified
> c"\MinGW\bin\make.exe **** [gsm/src/add.o] Error 2


hmm, OK, this is interesting.  

Your build environment is different from mine, in that you're using a
"make" provided by MinGW, as opposed to the cygwin make.  Their make
might be broken in some way, although I think someone built sucessfully
with MinGW with "msys" installed.

The way my environment is set up, I have cygwin installed, and MinGW
installed, and then I have the MinGW tools installed ahead of the cygwin
stuff in my path.  I.e. my path is:


        /cygdrive/c/MINGW/bin:/usr/local/bin:/usr/bin:/bin:/cygdrive/c/SPRY/BIN:/cygdriv
        e/c/WINDOWS:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS/system32/WBEM:/cygd
        rive/c/Program Files/Real/Helix Producer
        Basic:/cygdrive/c/Program Files/Microso
        ft Visual Studio/Common/Tools/WinNT:/cygdrive/c/Program
        Files/Microsoft Visual S
        tudio/Common/MSDev98/Bin:/cygdrive/c/Program Files/Microsoft
        Visual Studio/Commo
        n/Tools:/cygdrive/c/Program Files/Microsoft Visual
        Studio/VC98/bin


(all that's really important is that the MinGW binaries come before the
cygwin binaries).

Then, I run a shell from cygwin (using the icon the cygwin install
leaves on the desktop, which gives me a terminal running bash), and do
the make from there.

But, my MINGW directory doesn't have "make.exe" in it.  There's a
mingw32-make.exe, but the purposely don't call it "make.exe", because it
sucks :)

I can't understand the particular error your make gave you, but I don't
know what file it's talking about.  (I think the note is that it's
trying to make gsm/src/add.o, which is should do from the implicit rule
from gsm/src/add.c).


So, I think the easiest way to get you going is to get yourself cygwin
(just run http://cygwin.com/setup.exe), find out what that make you're
using is and get rid of it, then build with cygwin's tools (except for
the compiler, for that use mingw).

The rest of your research, below, is unlikely to get you anywhere
helpful.  I don't maintain any of the other Makefiles other than
lib/Makefile simpleclient/testcall/Makefile and
simpleclient/wx/Makefile.  Even if those other Makefiles work, they'll
give you some library which isn't going to help you.


Also, please post to the mailing list; other people are working through
the same thing (]data[ from IRC, for example, just got a whole "wx.exe"
build going himself), and the discussion can either help others, or
perhaps others can help you.

-SteveK


> Research:
> went to iaxclient/lib/gsm/src: there is no add.o, just add.c
> There is a "makefile" here, so I typed "make clean"; results: +ve
>  
> Hacking: from iaxclient/lib/gsm, typed "make".  Results: +ve
> Went back to iaxclient/lib typed: "make"
> Resulting message:
> The same but with code.o missing instead of add.o
>  
> I will greatly appreciate your guidance through these difficulties.
>  
>  
> Regards,
> Uriel
> 
>         -----Original Message-----
>         From: iax...@li...
>         [mailto:iax...@li...]On Behalf
>         Of Steve Kann
>         Sent: Wednesday, June 11, 2003 10:21 AM
>         To: ur...@ad...
>         Cc: iaxclient devel
>         Subject: RE: [Iaxclient-devel] Compiling with MinGW/Cygwin
>         
>         
>         Uriel,
>         
>             There's three "maintained" makefiles within the project. 
>         The Makefile in iaxclient/lib, and the Makefiles in
>         simpleclient/testcall and simpleclient/wx.
>         
>         Both of the simpleclient/*/Makefiles will call the Makefile in
>         lib to make the library, as both clients use the library, and
>         thus require the library (libiaxclient.a) to be built.
>         
>         So, from clean CVS, you should be able to just go to
>         simpleclient/testcall, and type "make".
>         
>         However, if you've tried other things, I'd say you'd be best
>         off going to iaxclient/lib, typing "make clean", then "make". 
>         Then, go to the client you want to make and type "make clean",
>         "make".
>         
>         (the client Makefiles won't "clean" the library).
>         
>         First, try making "testcall", since for "wx", you'll also need
>         to have wxwindows installed, etc.  Definately a better first
>         step is to compile testcall.
>         
>         And yes, there's no install targets in the Makefiles.  You
>         don't need to install the library, and the executable targets
>         are standalone (i.e. for wx, there's "wx.exe" for windows,
>         "wx" for linux, and "wx.app" for MacOSX).
>         
>         
>         
>         On Wed, 2003-06-11 at 00:00, Uriel Carrasquilla wrote: 
>         
>         > Steve:
>         > I am having a hard time compiling with MinGW and Gygwin.
>         > I downloaded the CVS from Monday night.
>         > I went to the /iaxclient/simpleclient/wx  (where there is a
>         > Makefile) and typed: make
>         > Problems developed in the lib/gsm.  I can see in the
>         > wx/Makefile that we are trying to make iaxclient.a from
>         > lib/gsm.  So I went over and type
>         > make iaxclient.a
>         > could not find a file.  So I went to the gsm subdirectory
>         > and somewhere in there there was another makefile (lower
>         > case which is normally a second choice for make).  I did a
>         > make.
>         > Went back one leve to lib/gsm and executed make 
>         > Got another file missing.  
>         >  
>         > My question: is there a sequence of "make" that I have to
>         > execute?
>         > what would it be?
>         > I could not see and "install" in any of the Makefile.  is it
>         > by design?
>         > Regards,
>         > Uriel
>         > 
>         >         -----Original Message-----
>         >         From: iax...@li...
>         >         [mailto:iax...@li...]On Behalf Of Steve Kann
>         >         Sent: Tuesday, June 10, 2003 7:48 PM
>         >         To: iaxclient devel
>         >         Subject: [Iaxclient-devel] some updates, and Ideas
>         >         for contributions..
>         >         
>         >         
>         >         1) (most relevant): put iax call processing
>         >         (including audio) into a separate thread.  This
>         >         helps the most when you do things that block the GUI
>         >         thread, like resizing the window (Win32 only?).  And
>         >         it seems to also help the Mac a bit(*)
>         >         
>         >         (*) The volume meters, implemented with progress
>         >         bars via wxwindows on the mac, eat a lot of CPU for
>         >         their animation.  Not that it doesn't look good.  I
>         >         think that this caused some skips on the Mac.
>         >         
>         >         2) Fixed the DTMF buttons that I broke sometime
>         >         today or last night.
>         >         
>         >         3) Fixed PTT a bit.  (looking for feedback on how
>         >         this works).
>         >         
>         >         Also, due to a byproduct of the way I did things, if
>         >         you enable then disable PTT, you'll also be enabling
>         >         silence detection/suppression.  This will make the
>         >         client not spit out any audio frames until the input
>         >         audio level reaches -40 DB.  
>         >         
>         >         There's been a lot of interest here on the list and
>         >         on IRC from a growing community.  That's cool. 
>         >         People asked what they can help with, so here's some
>         >         ideas for adventurous souls:
>         >         
>         >         
>         >         1) IAX2:  You can build it via my Makefiles by
>         >         setting IAXVER=2 at the top of the  
>         >                        library Makefile, or building the
>         >         library by running "make IAXVER=2".  It 
>         >                        doesn't work quite right, though, so
>         >         if someone could try and figure that one 
>         >                        out, it would be good.  Once it's
>         >         working, IAX2 should offer us a bunch of 
>         >                        quality improvements, especially over
>         >         the internet.
>         >         
>         >         2) Registration:  People out there want this, and it
>         >         will make the apps/library more     
>         >                        useful to the community.  Shouldn't
>         >         be too hard, but will need to be a bit     
>         >                        careful about keeping track of calls,
>         >         sessions, peers, etc.
>         >         
>         >         3) A maintainer for VC++ Makefiles and/or .dsw
>         >         files.  I don't know this stuff, and I 
>         >                       don't like tools you need your mouse
>         >         for.  But, if it helps people get more 
>         >                       involved, I'm all for keeping a
>         >         current .dsw/dsp or whatever file in CVS, one 
>         >                       for each of the Makefiles, I guess
>         >         (lib, testcall, wx).
>         >         
>         >         4) Exposing Audio Settings:  Make controls (library
>         >         functions and GUI) for enumerating and choosing
>         >         audio input/output devices.  This may require either
>         >         moving to the standard portaudio callback interface,
>         >         or hacking pablio to allow you to choose particular
>         >         devices.  Also, expose setting the input and output
>         >         "levels".  It's probably best to allow them to
>         >         change this while the app is running, so you'll need
>         >         to close/re-open the audio device, etc.
>         >         
>         >         5) MacOSX Mono audio problem:  Currently MacOSX
>         >         audio comes only out of the left channel.  Seems
>         >         like a portaudio problem to track down.
>         >         
>         >         6) silence detection / dynamic range compression: 
>         >         Figure out good values or algorithms to make the
>         >         client automatically (a) not send any packets when
>         >         there's no speech, (b) put out good consistent
>         >         volume when there is speech, even if people don't
>         >         have consistent microphone/soundcard settings, use
>         >         laptop microphones or nice headsets.
>         >         
>         >         7) Additional codec support:  I'd start with uLaw,
>         >         to make some #iaxclient user happy, but also because
>         >         it's pretty easy to implement, then also try iLBC
>         >         and/or Speex.  Probably want one way for the user to
>         >         choose their preferred codec.
>         >         
>         >         Hmm, that's a bunch of stuff :)
>         >         
>         >         If anyone wants to step up for this stuff, let the
>         >         list know, so we all don't duplicate each other's
>         >         work.
>         >         
>         >         
>         >         Happy IAX clienting!
>         >         
>         >         -SteveK
>         >         
>         >         
>         >         
>         >         
>         >         
>         >         -- 
>         >           Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
>         >                         HorizonLive.com - collaborate . interact . learn
>         >            "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."
>         
>         -- 
>           Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
>                         HorizonLive.com - collaborate . interact . learn
>            "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

[Iaxclient-devel] iaxclient updates...

[Steve K. <st...@st...>]

I've done some work on audio processing a bit, and the results seem to
be better.

There's three main changes:
1) Changed the companding parameters a bit, to cut down background
noise, and level out speaking volume a bit.

2) Implemented an "auto" silence suppression setting, where it keeps
track of the noise floor, and considers everything within 5db of the
floor to be silence.

3) Implemented a 40ms delay within the compander/silence detector, to
co-incide with the 40ms attack timing, so you don't lose the first 40ms
of non-silence (basically makes companding/silence detection predective
as opposed to reactive).



-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

RE: [Iaxclient-devel] Compiling with MinGW/Cygwin

[Steve K. <st...@st...>]

Uriel,

    There's three "maintained" makefiles within the project.  The
Makefile in iaxclient/lib, and the Makefiles in simpleclient/testcall
and simpleclient/wx.

Both of the simpleclient/*/Makefiles will call the Makefile in lib to
make the library, as both clients use the library, and thus require the
library (libiaxclient.a) to be built.

So, from clean CVS, you should be able to just go to
simpleclient/testcall, and type "make".

However, if you've tried other things, I'd say you'd be best off going
to iaxclient/lib, typing "make clean", then "make".  Then, go to the
client you want to make and type "make clean", "make".

(the client Makefiles won't "clean" the library).

First, try making "testcall", since for "wx", you'll also need to have
wxwindows installed, etc.  Definately a better first step is to compile
testcall.

And yes, there's no install targets in the Makefiles.  You don't need to
install the library, and the executable targets are standalone (i.e. for
wx, there's "wx.exe" for windows, "wx" for linux, and "wx.app" for
MacOSX).



On Wed, 2003-06-11 at 00:00, Uriel Carrasquilla wrote:

> Steve:
> I am having a hard time compiling with MinGW and Gygwin.
> I downloaded the CVS from Monday night.
> I went to the /iaxclient/simpleclient/wx  (where there is a Makefile)
> and typed: make
> Problems developed in the lib/gsm.  I can see in the wx/Makefile that
> we are trying to make iaxclient.a from lib/gsm.  So I went over and
> type
> make iaxclient.a
> could not find a file.  So I went to the gsm subdirectory and
> somewhere in there there was another makefile (lower case which is
> normally a second choice for make).  I did a make.
> Went back one leve to lib/gsm and executed make 
> Got another file missing.  
>  
> My question: is there a sequence of "make" that I have to execute?
> what would it be?
> I could not see and "install" in any of the Makefile.  is it by
> design?
> Regards,
> Uriel
> 
>         -----Original Message-----
>         From: iax...@li...
>         [mailto:iax...@li...]On Behalf
>         Of Steve Kann
>         Sent: Tuesday, June 10, 2003 7:48 PM
>         To: iaxclient devel
>         Subject: [Iaxclient-devel] some updates, and Ideas for
>         contributions..
>         
>         
>         1) (most relevant): put iax call processing (including audio)
>         into a separate thread.  This helps the most when you do
>         things that block the GUI thread, like resizing the window
>         (Win32 only?).  And it seems to also help the Mac a bit(*)
>         
>         (*) The volume meters, implemented with progress bars via
>         wxwindows on the mac, eat a lot of CPU for their animation. 
>         Not that it doesn't look good.  I think that this caused some
>         skips on the Mac.
>         
>         2) Fixed the DTMF buttons that I broke sometime today or last
>         night.
>         
>         3) Fixed PTT a bit.  (looking for feedback on how this works).
>         
>         Also, due to a byproduct of the way I did things, if you
>         enable then disable PTT, you'll also be enabling silence
>         detection/suppression.  This will make the client not spit out
>         any audio frames until the input audio level reaches -40 DB.  
>         
>         There's been a lot of interest here on the list and on IRC
>         from a growing community.  That's cool.  People asked what
>         they can help with, so here's some ideas for adventurous
>         souls:
>         
>         
>         1) IAX2:  You can build it via my Makefiles by setting
>         IAXVER=2 at the top of the  
>                        library Makefile, or building the library by
>         running "make IAXVER=2".  It 
>                        doesn't work quite right, though, so if someone
>         could try and figure that one 
>                        out, it would be good.  Once it's working, IAX2
>         should offer us a bunch of 
>                        quality improvements, especially over the
>         internet.
>         
>         2) Registration:  People out there want this, and it will make
>         the apps/library more     
>                        useful to the community.  Shouldn't be too
>         hard, but will need to be a bit     
>                        careful about keeping track of calls, sessions,
>         peers, etc.
>         
>         3) A maintainer for VC++ Makefiles and/or .dsw files.  I don't
>         know this stuff, and I 
>                       don't like tools you need your mouse for.  But,
>         if it helps people get more 
>                       involved, I'm all for keeping a current .dsw/dsp
>         or whatever file in CVS, one 
>                       for each of the Makefiles, I guess (lib,
>         testcall, wx).
>         
>         4) Exposing Audio Settings:  Make controls (library functions
>         and GUI) for enumerating and choosing audio input/output
>         devices.  This may require either moving to the standard
>         portaudio callback interface, or hacking pablio to allow you
>         to choose particular devices.  Also, expose setting the input
>         and output "levels".  It's probably best to allow them to
>         change this while the app is running, so you'll need to
>         close/re-open the audio device, etc.
>         
>         5) MacOSX Mono audio problem:  Currently MacOSX audio comes
>         only out of the left channel.  Seems like a portaudio problem
>         to track down.
>         
>         6) silence detection / dynamic range compression:  Figure out
>         good values or algorithms to make the client automatically (a)
>         not send any packets when there's no speech, (b) put out good
>         consistent volume when there is speech, even if people don't
>         have consistent microphone/soundcard settings, use laptop
>         microphones or nice headsets.
>         
>         7) Additional codec support:  I'd start with uLaw, to make
>         some #iaxclient user happy, but also because it's pretty easy
>         to implement, then also try iLBC and/or Speex.  Probably want
>         one way for the user to choose their preferred codec.
>         
>         Hmm, that's a bunch of stuff :)
>         
>         If anyone wants to step up for this stuff, let the list know,
>         so we all don't duplicate each other's work.
>         
>         
>         Happy IAX clienting!
>         
>         -SteveK
>         
>         
>         
>         
>         
>         -- 
>           Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
>                         HorizonLive.com - collaborate . interact . learn
>            "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

[Iaxclient-devel] some updates, and Ideas for contributions..

[Steve K. <st...@st...>]

1) (most relevant): put iax call processing (including audio) into a
separate thread.  This helps the most when you do things that block the
GUI thread, like resizing the window (Win32 only?).  And it seems to
also help the Mac a bit(*)

(*) The volume meters, implemented with progress bars via wxwindows on
the mac, eat a lot of CPU for their animation.  Not that it doesn't look
good.  I think that this caused some skips on the Mac.

2) Fixed the DTMF buttons that I broke sometime today or last night.

3) Fixed PTT a bit.  (looking for feedback on how this works).

Also, due to a byproduct of the way I did things, if you enable then
disable PTT, you'll also be enabling silence detection/suppression. 
This will make the client not spit out any audio frames until the input
audio level reaches -40 DB.  

There's been a lot of interest here on the list and on IRC from a
growing community.  That's cool.  People asked what they can help with,
so here's some ideas for adventurous souls:


1) IAX2:  You can build it via my Makefiles by setting IAXVER=2 at the
top of the  
               library Makefile, or building the library by running
"make IAXVER=2".  It 
               doesn't work quite right, though, so if someone could try
and figure that one 
               out, it would be good.  Once it's working, IAX2 should
offer us a bunch of 
               quality improvements, especially over the internet.

2) Registration:  People out there want this, and it will make the
apps/library more     
               useful to the community.  Shouldn't be too hard, but will
need to be a bit     
               careful about keeping track of calls, sessions, peers,
etc.

3) A maintainer for VC++ Makefiles and/or .dsw files.  I don't know this
stuff, and I 
              don't like tools you need your mouse for.  But, if it
helps people get more 
              involved, I'm all for keeping a current .dsw/dsp or
whatever file in CVS, one 
              for each of the Makefiles, I guess (lib, testcall, wx).

4) Exposing Audio Settings:  Make controls (library functions and GUI)
for enumerating and choosing audio input/output devices.  This may
require either moving to the standard portaudio callback interface, or
hacking pablio to allow you to choose particular devices.  Also, expose
setting the input and output "levels".  It's probably best to allow them
to change this while the app is running, so you'll need to close/re-open
the audio device, etc.

5) MacOSX Mono audio problem:  Currently MacOSX audio comes only out of
the left channel.  Seems like a portaudio problem to track down.

6) silence detection / dynamic range compression:  Figure out good
values or algorithms to make the client automatically (a) not send any
packets when there's no speech, (b) put out good consistent volume when
there is speech, even if people don't have consistent
microphone/soundcard settings, use laptop microphones or nice headsets.

7) Additional codec support:  I'd start with uLaw, to make some
#iaxclient user happy, but also because it's pretty easy to implement,
then also try iLBC and/or Speex.  Probably want one way for the user to
choose their preferred codec.

Hmm, that's a bunch of stuff :)

If anyone wants to step up for this stuff, let the list know, so we all
don't duplicate each other's work.


Happy IAX clienting!

-SteveK





-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

[Iaxclient-devel] libiaxclient VC version.

[Babar S. <bab...@ya...>]

I did whole libiaxclient library in VC. and its easy
to port the code in VC because of good coding style by
Steve.  and there is no need of cygwin etc if we just
did all in VC and also I did a same testcall.exe with
that lib.


Great job Steve. Keep it up the good work



"libiaxclient.mak" (Debug version)

--------------------xxxxxxxxxxx-------------------
# Microsoft Developer Studio Generated NMAKE File,
Based on libiaxclient.dsp
!IF "$(CFG)" == ""
CFG=libiaxclient - Win32 Debug
!MESSAGE No configuration specified. Defaulting to
libiaxclient - Win32 Debug.
!ENDIF 

!IF "$(CFG)" != "libiaxclient - Win32 Release" &&
"$(CFG)" != "libiaxclient - Win32 Debug"
!MESSAGE Invalid configuration "$(CFG)" specified.
!MESSAGE You can specify a configuration when running
NMAKE
!MESSAGE by defining the macro CFG on the command
line. For example:
!MESSAGE 
!MESSAGE NMAKE /f "libiaxclient.mak" CFG="libiaxclient
- Win32 Debug"
!MESSAGE 
!MESSAGE Possible choices for configuration are:
!MESSAGE 
!MESSAGE "libiaxclient - Win32 Release" (based on
"Win32 (x86) Static Library")
!MESSAGE "libiaxclient - Win32 Debug" (based on "Win32
(x86) Static Library")
!MESSAGE 
!ERROR An invalid configuration is specified.
!ENDIF 

!IF "$(OS)" == "Windows_NT"
NULL=
!ELSE 
NULL=nul
!ENDIF 

CPP=cl.exe
RSC=rc.exe

!IF  "$(CFG)" == "libiaxclient - Win32 Release"

OUTDIR=.\Release
INTDIR=.\Release
# Begin Custom Macros
OutDir=.\Release
# End Custom Macros

ALL : "$(OUTDIR)\libiaxclient.lib"


CLEAN :
	-@erase "$(INTDIR)\add.obj"
	-@erase "$(INTDIR)\audio_encode.obj"
	-@erase "$(INTDIR)\audio_portaudio.obj"
	-@erase "$(INTDIR)\audio_win32.obj"
	-@erase "$(INTDIR)\code.obj"
	-@erase "$(INTDIR)\compand.obj"
	-@erase "$(INTDIR)\debug.obj"
	-@erase "$(INTDIR)\decode.obj"
	-@erase "$(INTDIR)\gsm_create.obj"
	-@erase "$(INTDIR)\gsm_decode.obj"
	-@erase "$(INTDIR)\gsm_destroy.obj"
	-@erase "$(INTDIR)\gsm_encode.obj"
	-@erase "$(INTDIR)\gsm_explode.obj"
	-@erase "$(INTDIR)\gsm_implode.obj"
	-@erase "$(INTDIR)\gsm_option.obj"
	-@erase "$(INTDIR)\gsm_print.obj"
	-@erase "$(INTDIR)\iax.obj"
	-@erase "$(INTDIR)\iaxclient_lib.obj"
	-@erase "$(INTDIR)\long_term.obj"
	-@erase "$(INTDIR)\lpc.obj"
	-@erase "$(INTDIR)\md5.obj"
	-@erase "$(INTDIR)\pa_lib.obj"
	-@erase "$(INTDIR)\pa_win_wmme.obj"
	-@erase "$(INTDIR)\pablio.obj"
	-@erase "$(INTDIR)\preprocess.obj"
	-@erase "$(INTDIR)\resample.obj"
	-@erase "$(INTDIR)\ringbuffer.obj"
	-@erase "$(INTDIR)\rpe.obj"
	-@erase "$(INTDIR)\short_term.obj"
	-@erase "$(INTDIR)\soxcompat.obj"
	-@erase "$(INTDIR)\table.obj"
	-@erase "$(INTDIR)\vc60.idb"
	-@erase "$(INTDIR)\winfuncs.obj"
	-@erase "$(OUTDIR)\libiaxclient.lib"

"$(OUTDIR)" :
    if not exist "$(OUTDIR)/$(NULL)" mkdir "$(OUTDIR)"

CPP_PROJ=/nologo /ML /W3 /GX /O2 /D "WIN32" /D
"NDEBUG" /D "_MBCS" /D "_LIB"
/Fp"$(INTDIR)\libiaxclient.pch" /Yu"stdafx.h"
/Fo"$(INTDIR)\\" /Fd"$(INTDIR)\\" /FD /c 
BSC32=bscmake.exe
BSC32_FLAGS=/nologo /o"$(OUTDIR)\libiaxclient.bsc" 
BSC32_SBRS= \
	
LIB32=link.exe -lib
LIB32_FLAGS=/nologo /out:"$(OUTDIR)\libiaxclient.lib" 
LIB32_OBJS= \
	"$(INTDIR)\add.obj" \
	"$(INTDIR)\code.obj" \
	"$(INTDIR)\table.obj" \
	"$(INTDIR)\gsm_create.obj" \
	"$(INTDIR)\gsm_decode.obj" \
	"$(INTDIR)\gsm_destroy.obj" \
	"$(INTDIR)\gsm_encode.obj" \
	"$(INTDIR)\gsm_explode.obj" \
	"$(INTDIR)\gsm_implode.obj" \
	"$(INTDIR)\gsm_option.obj" \
	"$(INTDIR)\gsm_print.obj" \
	"$(INTDIR)\long_term.obj" \
	"$(INTDIR)\lpc.obj" \
	"$(INTDIR)\preprocess.obj" \
	"$(INTDIR)\rpe.obj" \
	"$(INTDIR)\short_term.obj" \
	"$(INTDIR)\debug.obj" \
	"$(INTDIR)\pa_lib.obj" \
	"$(INTDIR)\pablio.obj" \
	"$(INTDIR)\ringbuffer.obj" \
	"$(INTDIR)\winfuncs.obj" \
	"$(INTDIR)\audio_portaudio.obj" \
	"$(INTDIR)\audio_win32.obj" \
	"$(INTDIR)\iaxclient_lib.obj" \
	"$(INTDIR)\audio_encode.obj" \
	"$(INTDIR)\pa_win_wmme.obj" \
	"$(INTDIR)\compand.obj" \
	"$(INTDIR)\resample.obj" \
	"$(INTDIR)\soxcompat.obj" \
	"$(INTDIR)\md5.obj" \
	"$(INTDIR)\iax.obj" \
	"$(INTDIR)\decode.obj"

"$(OUTDIR)\libiaxclient.lib" : "$(OUTDIR)" $(DEF_FILE)
$(LIB32_OBJS)
    $(LIB32) @<<
  $(LIB32_FLAGS) $(DEF_FLAGS) $(LIB32_OBJS)
<<

!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"

OUTDIR=.\Debug
INTDIR=.\Debug
# Begin Custom Macros
OutDir=.\Debug
# End Custom Macros

ALL : "$(OUTDIR)\libiaxclient.lib"
"$(OUTDIR)\libiaxclient.bsc"


CLEAN :
	-@erase "$(INTDIR)\add.obj"
	-@erase "$(INTDIR)\add.sbr"
	-@erase "$(INTDIR)\audio_encode.obj"
	-@erase "$(INTDIR)\audio_encode.sbr"
	-@erase "$(INTDIR)\audio_portaudio.obj"
	-@erase "$(INTDIR)\audio_portaudio.sbr"
	-@erase "$(INTDIR)\audio_win32.obj"
	-@erase "$(INTDIR)\audio_win32.sbr"
	-@erase "$(INTDIR)\code.obj"
	-@erase "$(INTDIR)\code.sbr"
	-@erase "$(INTDIR)\compand.obj"
	-@erase "$(INTDIR)\compand.sbr"
	-@erase "$(INTDIR)\debug.obj"
	-@erase "$(INTDIR)\debug.sbr"
	-@erase "$(INTDIR)\decode.obj"
	-@erase "$(INTDIR)\decode.sbr"
	-@erase "$(INTDIR)\gsm_create.obj"
	-@erase "$(INTDIR)\gsm_create.sbr"
	-@erase "$(INTDIR)\gsm_decode.obj"
	-@erase "$(INTDIR)\gsm_decode.sbr"
	-@erase "$(INTDIR)\gsm_destroy.obj"
	-@erase "$(INTDIR)\gsm_destroy.sbr"
	-@erase "$(INTDIR)\gsm_encode.obj"
	-@erase "$(INTDIR)\gsm_encode.sbr"
	-@erase "$(INTDIR)\gsm_explode.obj"
	-@erase "$(INTDIR)\gsm_explode.sbr"
	-@erase "$(INTDIR)\gsm_implode.obj"
	-@erase "$(INTDIR)\gsm_implode.sbr"
	-@erase "$(INTDIR)\gsm_option.obj"
	-@erase "$(INTDIR)\gsm_option.sbr"
	-@erase "$(INTDIR)\gsm_print.obj"
	-@erase "$(INTDIR)\gsm_print.sbr"
	-@erase "$(INTDIR)\iax.obj"
	-@erase "$(INTDIR)\iax.sbr"
	-@erase "$(INTDIR)\iaxclient_lib.obj"
	-@erase "$(INTDIR)\iaxclient_lib.sbr"
	-@erase "$(INTDIR)\long_term.obj"
	-@erase "$(INTDIR)\long_term.sbr"
	-@erase "$(INTDIR)\lpc.obj"
	-@erase "$(INTDIR)\lpc.sbr"
	-@erase "$(INTDIR)\md5.obj"
	-@erase "$(INTDIR)\md5.sbr"
	-@erase "$(INTDIR)\pa_lib.obj"
	-@erase "$(INTDIR)\pa_lib.sbr"
	-@erase "$(INTDIR)\pa_win_wmme.obj"
	-@erase "$(INTDIR)\pa_win_wmme.sbr"
	-@erase "$(INTDIR)\pablio.obj"
	-@erase "$(INTDIR)\pablio.sbr"
	-@erase "$(INTDIR)\preprocess.obj"
	-@erase "$(INTDIR)\preprocess.sbr"
	-@erase "$(INTDIR)\resample.obj"
	-@erase "$(INTDIR)\resample.sbr"
	-@erase "$(INTDIR)\ringbuffer.obj"
	-@erase "$(INTDIR)\ringbuffer.sbr"
	-@erase "$(INTDIR)\rpe.obj"
	-@erase "$(INTDIR)\rpe.sbr"
	-@erase "$(INTDIR)\short_term.obj"
	-@erase "$(INTDIR)\short_term.sbr"
	-@erase "$(INTDIR)\soxcompat.obj"
	-@erase "$(INTDIR)\soxcompat.sbr"
	-@erase "$(INTDIR)\table.obj"
	-@erase "$(INTDIR)\table.sbr"
	-@erase "$(INTDIR)\vc60.idb"
	-@erase "$(INTDIR)\vc60.pdb"
	-@erase "$(INTDIR)\winfuncs.obj"
	-@erase "$(INTDIR)\winfuncs.sbr"
	-@erase "$(OUTDIR)\libiaxclient.bsc"
	-@erase "$(OUTDIR)\libiaxclient.lib"

"$(OUTDIR)" :
    if not exist "$(OUTDIR)/$(NULL)" mkdir "$(OUTDIR)"

CPP_PROJ=/nologo /MLd /W3 /Gm /GX /ZI /Od /D "WIN32"
/D "_DEBUG" /D "_MBCS" /D "_LIB" /FR"$(INTDIR)\\"
/Fo"$(INTDIR)\\" /Fd"$(INTDIR)\\" /FD /GZ /c 
BSC32=bscmake.exe
BSC32_FLAGS=/nologo /o"$(OUTDIR)\libiaxclient.bsc" 
BSC32_SBRS= \
	"$(INTDIR)\add.sbr" \
	"$(INTDIR)\code.sbr" \
	"$(INTDIR)\table.sbr" \
	"$(INTDIR)\gsm_create.sbr" \
	"$(INTDIR)\gsm_decode.sbr" \
	"$(INTDIR)\gsm_destroy.sbr" \
	"$(INTDIR)\gsm_encode.sbr" \
	"$(INTDIR)\gsm_explode.sbr" \
	"$(INTDIR)\gsm_implode.sbr" \
	"$(INTDIR)\gsm_option.sbr" \
	"$(INTDIR)\gsm_print.sbr" \
	"$(INTDIR)\long_term.sbr" \
	"$(INTDIR)\lpc.sbr" \
	"$(INTDIR)\preprocess.sbr" \
	"$(INTDIR)\rpe.sbr" \
	"$(INTDIR)\short_term.sbr" \
	"$(INTDIR)\debug.sbr" \
	"$(INTDIR)\pa_lib.sbr" \
	"$(INTDIR)\pablio.sbr" \
	"$(INTDIR)\ringbuffer.sbr" \
	"$(INTDIR)\winfuncs.sbr" \
	"$(INTDIR)\audio_portaudio.sbr" \
	"$(INTDIR)\audio_win32.sbr" \
	"$(INTDIR)\iaxclient_lib.sbr" \
	"$(INTDIR)\audio_encode.sbr" \
	"$(INTDIR)\pa_win_wmme.sbr" \
	"$(INTDIR)\compand.sbr" \
	"$(INTDIR)\resample.sbr" \
	"$(INTDIR)\soxcompat.sbr" \
	"$(INTDIR)\md5.sbr" \
	"$(INTDIR)\iax.sbr" \
	"$(INTDIR)\decode.sbr"

"$(OUTDIR)\libiaxclient.bsc" : "$(OUTDIR)"
$(BSC32_SBRS)
    $(BSC32) @<<
  $(BSC32_FLAGS) $(BSC32_SBRS)
<<

LIB32=link.exe -lib
LIB32_FLAGS=/nologo /out:"$(OUTDIR)\libiaxclient.lib" 
LIB32_OBJS= \
	"$(INTDIR)\add.obj" \
	"$(INTDIR)\code.obj" \
	"$(INTDIR)\table.obj" \
	"$(INTDIR)\gsm_create.obj" \
	"$(INTDIR)\gsm_decode.obj" \
	"$(INTDIR)\gsm_destroy.obj" \
	"$(INTDIR)\gsm_encode.obj" \
	"$(INTDIR)\gsm_explode.obj" \
	"$(INTDIR)\gsm_implode.obj" \
	"$(INTDIR)\gsm_option.obj" \
	"$(INTDIR)\gsm_print.obj" \
	"$(INTDIR)\long_term.obj" \
	"$(INTDIR)\lpc.obj" \
	"$(INTDIR)\preprocess.obj" \
	"$(INTDIR)\rpe.obj" \
	"$(INTDIR)\short_term.obj" \
	"$(INTDIR)\debug.obj" \
	"$(INTDIR)\pa_lib.obj" \
	"$(INTDIR)\pablio.obj" \
	"$(INTDIR)\ringbuffer.obj" \
	"$(INTDIR)\winfuncs.obj" \
	"$(INTDIR)\audio_portaudio.obj" \
	"$(INTDIR)\audio_win32.obj" \
	"$(INTDIR)\iaxclient_lib.obj" \
	"$(INTDIR)\audio_encode.obj" \
	"$(INTDIR)\pa_win_wmme.obj" \
	"$(INTDIR)\compand.obj" \
	"$(INTDIR)\resample.obj" \
	"$(INTDIR)\soxcompat.obj" \
	"$(INTDIR)\md5.obj" \
	"$(INTDIR)\iax.obj" \
	"$(INTDIR)\decode.obj"

"$(OUTDIR)\libiaxclient.lib" : "$(OUTDIR)" $(DEF_FILE)
$(LIB32_OBJS)
    $(LIB32) @<<
  $(LIB32_FLAGS) $(DEF_FLAGS) $(LIB32_OBJS)
<<

!ENDIF 

.c{$(INTDIR)}.obj::
   $(CPP) @<<
   $(CPP_PROJ) $< 
<<

.cpp{$(INTDIR)}.obj::
   $(CPP) @<<
   $(CPP_PROJ) $< 
<<

.cxx{$(INTDIR)}.obj::
   $(CPP) @<<
   $(CPP_PROJ) $< 
<<

.c{$(INTDIR)}.sbr::
   $(CPP) @<<
   $(CPP_PROJ) $< 
<<

.cpp{$(INTDIR)}.sbr::
   $(CPP) @<<
   $(CPP_PROJ) $< 
<<

.cxx{$(INTDIR)}.sbr::
   $(CPP) @<<
   $(CPP_PROJ) $< 
<<


!IF "$(NO_EXTERNAL_DEPS)" != "1"
!IF EXISTS("libiaxclient.dep")
!INCLUDE "libiaxclient.dep"
!ELSE 
!MESSAGE Warning: cannot find "libiaxclient.dep"
!ENDIF 
!ENDIF 


!IF "$(CFG)" == "libiaxclient - Win32 Release" ||
"$(CFG)" == "libiaxclient - Win32 Debug"
SOURCE=..\lib\gsm\src\add.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\add.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\add.obj"	"$(INTDIR)\add.sbr" : $(SOURCE)
"$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\audio_encode.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\audio_encode.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\audio_encode.obj"
"$(INTDIR)\audio_encode.sbr" : $(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\audio_portaudio.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\audio_portaudio.obj" : $(SOURCE)
"$(INTDIR)" "$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\audio_portaudio.obj"
"$(INTDIR)\audio_portaudio.sbr" : $(SOURCE)
"$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\audio_win32.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\audio_win32.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\audio_win32.obj"
"$(INTDIR)\audio_win32.sbr" : $(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\gsm\src\code.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\code.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\code.obj"	"$(INTDIR)\code.sbr" : $(SOURCE)
"$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\sox\compand.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\compand.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\compand.obj"	"$(INTDIR)\compand.sbr" :
$(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\gsm\src\debug.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\debug.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\debug.obj"	"$(INTDIR)\debug.sbr" :
$(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\gsm\src\decode.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\decode.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\decode.obj"	"$(INTDIR)\decode.sbr" :
$(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\gsm\src\gsm_create.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\gsm_create.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\gsm_create.obj"	"$(INTDIR)\gsm_create.sbr"
: $(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\gsm\src\gsm_decode.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\gsm_decode.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\gsm_decode.obj"	"$(INTDIR)\gsm_decode.sbr"
: $(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\gsm\src\gsm_destroy.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\gsm_destroy.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\gsm_destroy.obj"
"$(INTDIR)\gsm_destroy.sbr" : $(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\gsm\src\gsm_encode.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\gsm_encode.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\gsm_encode.obj"	"$(INTDIR)\gsm_encode.sbr"
: $(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\gsm\src\gsm_explode.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\gsm_explode.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\gsm_explode.obj"
"$(INTDIR)\gsm_explode.sbr" : $(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\gsm\src\gsm_implode.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\gsm_implode.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\gsm_implode.obj"
"$(INTDIR)\gsm_implode.sbr" : $(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\gsm\src\gsm_option.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\gsm_option.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\gsm_option.obj"	"$(INTDIR)\gsm_option.sbr"
: $(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\gsm\src\gsm_print.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\gsm_print.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\gsm_print.obj"	"$(INTDIR)\gsm_print.sbr" :
$(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\libiax\src\iax.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\iax.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\iax.obj"	"$(INTDIR)\iax.sbr" : $(SOURCE)
"$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\iaxclient_lib.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\iaxclient_lib.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\iaxclient_lib.obj"
"$(INTDIR)\iaxclient_lib.sbr" : $(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\gsm\src\long_term.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\long_term.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\long_term.obj"	"$(INTDIR)\long_term.sbr" :
$(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\gsm\src\lpc.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\lpc.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\lpc.obj"	"$(INTDIR)\lpc.sbr" : $(SOURCE)
"$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\libiax\src\md5.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\md5.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\md5.obj"	"$(INTDIR)\md5.sbr" : $(SOURCE)
"$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\portaudio\pa_common\pa_lib.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\pa_lib.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\pa_lib.obj"	"$(INTDIR)\pa_lib.sbr" :
$(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\portaudio\pa_win_wmme\pa_win_wmme.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\pa_win_wmme.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\pa_win_wmme.obj"
"$(INTDIR)\pa_win_wmme.sbr" : $(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\portaudio\pablio\pablio.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\pablio.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\pablio.obj"	"$(INTDIR)\pablio.sbr" :
$(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\gsm\src\preprocess.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\preprocess.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\preprocess.obj"	"$(INTDIR)\preprocess.sbr"
: $(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\sox\resample.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\resample.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\resample.obj"	"$(INTDIR)\resample.sbr" :
$(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\portaudio\pablio\ringbuffer.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\ringbuffer.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\ringbuffer.obj"	"$(INTDIR)\ringbuffer.sbr"
: $(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\gsm\src\rpe.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\rpe.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\rpe.obj"	"$(INTDIR)\rpe.sbr" : $(SOURCE)
"$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\gsm\src\short_term.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\short_term.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\short_term.obj"	"$(INTDIR)\short_term.sbr"
: $(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\sox\soxcompat.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\soxcompat.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\soxcompat.obj"	"$(INTDIR)\soxcompat.sbr" :
$(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\gsm\src\table.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\table.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\table.obj"	"$(INTDIR)\table.sbr" :
$(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 

SOURCE=..\lib\winfuncs.c

!IF  "$(CFG)" == "libiaxclient - Win32 Release"


"$(INTDIR)\winfuncs.obj" : $(SOURCE) "$(INTDIR)"
"$(INTDIR)\libiaxclient.pch"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ELSEIF  "$(CFG)" == "libiaxclient - Win32 Debug"


"$(INTDIR)\winfuncs.obj"	"$(INTDIR)\winfuncs.sbr" :
$(SOURCE) "$(INTDIR)"
	$(CPP) $(CPP_PROJ) $(SOURCE)


!ENDIF 


!ENDIF 

--------------------xxxxxxxxxxx-------------------

__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com

Re: [Iaxclient-devel] couple of updates..

[Steve K. <st...@st...>]

On Tue, 2003-06-10 at 10:19, Faizan Naqvi wrote:


> Hi.
> 
> I have compiled the libiax and made enough changes to make it
> portable. Now it can be compiled as mutithreaded ilbrary from VC
> without any problem. I also had problems in using it with my IAX
> Client but now those are solved and it compiles and links fine with
> Win32 VC projects. I have it dialing and hanging up find on Asterisk.
> I didnt hear any sound , so I am gonna do it right now.
> 
> Why do you need Makefile for vc. Lets just use dsw files to get
> working. But yes there are a lot of things required to be done before
> you compile and moreover use it in VC projects.


makefiles or project files (dsw?).  Me, I'd prefer to use a nmake
makefile even for VC compilation, but that's because I don't like IDEs,
and prefer the command-line.  But if someone wants to contribute and
maintain project files (DSW?), I'll include those in CVS for the
community.


> If anyone is interested then I can upload it on my site later I fix
> the sound problem.


yes, please do.  If you'd like to see you changes in CVS, then please
send a unidiff (diff -u).  If it's small enough, you can send it right
here to the list.


Also, people can subscribe to iaxclient-cvs, to get notification on CVS
updates (with CVS comments, etc).

-SteveK


-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

Re: [Iaxclient-devel] need Some Help

[SYED O. A. <sye...@ho...>]

Hi

I'v downloaded CVS version of IAX Client u guyz did a great job but this API 
certainly lacks a Documentation anyways here is my current status .

I'v gone through Andre's IAXPhone  DLL and worked on it almost 2 weeks but 
finally realise that this DLL is not dependable and can make things 
wrong.now i have ur IAXLIB by extracting this "iaxclient.tar.gz" .i m really 
having problems in building its "lib" file. nad want to know steps in to 
properly build these libraries .

I have cygwin but dont know which package or distribution will be required 
for Mingw
Finally would u give me the URL from where ican download the source of ur 
latest GUI based IAX Client

Thanks and regards

Obaid Amin

>From: Steve Kann <st...@st...>
>To: SYED OBAID AMIN <sye...@ho...>
>CC: iaxclient devel <iax...@li...>
>Subject: Re: [Iaxclient-devel] need Som Help
>Date: 10 Jun 2003 10:17:20 -0400
>MIME-Version: 1.0
>Received: from m1.horizonlive.com ([208.185.78.2]) by 
>mc6-f12.law1.hotmail.com with Microsoft SMTPSVC(5.0.2195.5600); Tue, 10 Jun 
>2003 07:17:42 -0700
>Received: (qmail 22166 invoked from network); 10 Jun 2003 14:17:41 -0000
>Received: from canarsie.horizonlive.com (10.23.1.31)  by m1.horizonlive.com 
>with SMTP; 10 Jun 2003 14:17:41 -0000
>X-Message-Info: JGTYoYF78jEHjJx36Oi8+Q1OJDRSDidP
>In-Reply-To: <Law...@ho...>
>References: <Law...@ho...>
>Organization: horizonlive
>Message-Id: <105...@ca...>
>X-Mailer: Ximian Evolution 1.3.92 (Preview Release)
>Return-Path: st...@st...
>X-OriginalArrivalTime: 10 Jun 2003 14:17:42.0893 (UTC) 
>FILETIME=[0E8989D0:01C32F5B]
>
>Obaid,
>
>start by looking at the README in CVS.
>
>If you don't have CVS, look at the sourceforge directions.
>
>-SteveK
>
>
>On Tue, 2003-06-10 at 02:53, SYED OBAID AMIN wrote:
>
> > Hi All
> >
> > I  m graduate student and trying to build Win 32 IAX client as my 
>project,
> > would any 1 help me wat should b the staring point and where can i find 
>doc
> > about using LIBIAX API.
> >
> > Any help in this regard would b very helpful for me
> >
> > Obaid
> >
> > _________________________________________________________________
> > Help STOP SPAM with the new MSN 8 and get 2 months FREE*
> > http://join.msn.com/?page=features/junkmail
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> > thread debugger on the planet. Designed with thread debugging features
> > you've never dreamed of, try TotalView 6 free at www.etnus.com.
> > _______________________________________________
> > Iaxclient-devel mailing list
> > Iax...@li...
> > https://lists.sourceforge.net/lists/listinfo/iaxclient-devel
>
>--
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 
>533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed 
>Linux."

_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail

Re: [Iaxclient-devel] testcall fir MacOSX

[Steve K. <st...@st...>]

Panny,

The "Push to Talk" feature, added this morning, should help you on the
Mac.  Give it a try.

-SteveK


On Mon, 2003-06-09 at 06:08, Panny Malialis wrote:

> Hi,
> 
> I tested the wx binary it gave a just about useable call quality. It 
> was quite crackly to be honest :(
> 
> Also, using the standard mic and speakers the other end can (of course) 
> hear themselvees as their own voice is played straight back through the 
> mic on the ibook.
> Could there be an option to supress the mic when the other party is 
> speaking in order to avoid this situation?
> 
> The cvs does not compile for me
> 
> It dies with:
> 
> (cd ../../lib; make libiaxclient.a)
> make[1]: `libiaxclient.a' is up to date.
> `wx-config --cxx`  -I../../lib -I../../lib/libiax/src 
> -I../../lib/gsm/inc -I../../lib/portaudio/pa_common 
> -I../../lib/portaudio/pablio -Iinclude -g -DPOSIXSLEEP `wx-config 
> --cflags`  -c -o wx.o wx.cc
> /bin/sh: wx-config: command not found
> /bin/sh: wx-config: command not found
> /bin/sh: -I../../lib: No such file or directory
> make: *** [wx.o] Error 127
> 
> Thanks, and keep up the good work!!
> 
> Panny
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> thread debugger on the planet. Designed with thread debugging features
> you've never dreamed of, try TotalView 6 free at www.etnus.com.
> _______________________________________________
> Iaxclient-devel mailing list
> Iax...@li...
> https://lists.sourceforge.net/lists/listinfo/iaxclient-devel

-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."