I have been able to compile v19 with no problem on Cygwin. The test
programs for PortAudio work fine. I like it, and I am sure we can use it. 

The documentation for how to run PortAudio's configure script is not so
clear - I had to study the configure.in file closely to figure it out, but
once I had the right arguments for configure everything went automatically.
I had to run "./configure --with-host_os=cygwin" and also specify the audio
driver. I have not tried to build on Linux.

The actual makefiles in the distribution appear to be mostly out of date
and would require customization in order to work. I would guess that the
PortAudio developers themselves are now using autotools.


Original Message:
-----------------
From: John ffitch jpff@cs.bath.ac.uk
Date: Tue, 13 Jan 2004 15:12:49 +0000 (GMT)
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3925] Re: portaudio


Just d/loaded a fresh copy of portaudio_v19 but it does not compile 
(multiply defined functions).  I really was hoping to use v19.
==JPff


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

On Tue, 13 Jan 2004, gogins@pipeline.com wrote:

> I have been able to compile v19 with no problem on Cygwin. The test
> programs for PortAudio work fine. I like it, and I am sure we can use it. 
> 

It used to compile; had to correct the ANSI C at one stage but that was 
incorporated.  The current snapshot gets upset with two different 
definitions of a number of functions, after a 
./configure --with-alsa


It was always my intent to use PA v19, but it juist did not seem ready so 
I backed off.

I much prefer the blocking I/O variant, after all the hassles I have had 
with the Mac using callbacks.  As I understand it Pa_OpenStream is capable 
of opening a blocking stream, but no one has really tried it.  I have been 
lurking on teh portaudio mailing list for a year now, but am not really up 
to speed.

The priority decision for me at present is sound file library.  Still 
inclined to linsndfile as Erik seems amenable to developing if to suit.  I 
have not had time to get back to the soundin/diskin aspects of using 
libsndfile as I was away at teh weekend, and the students are getting 
jittery about the examinations next week.

==JPff