I quite quick with the CVS tools since I've been using them for 7ish years. I would happily maintain the pd/portaudio directory tree in the MAIN branch of CVS if you don't mind. Basically, just tell me which tarball to use and I'll check it in. It'll take me a couple minutes.
Plus, if there needs to be changes made to the portaudio sources, I think we should get in the habit of submitted patches to the portaudio people rather than just maintaining local changes.
.hc
On Jul 29, 2006, at 9:42 PM, Miller Puckette wrote:
If you're still using the 'main' Pd distribution, perhaps it would be easier to use the latest .src.tar.gz from my site instead... they're always self-contained. I find it difficult to keep the CVS repository complete since the tools are so cumbersome. Eventually I get the CVS version together, but to do so I usually have to spend a fair chunk of time checking for missing and extra files, as you've apparently just had the pleasure of doing as well...
cheers Miller
On Sat, Jul 29, 2006 at 07:32:04PM -0400, hans@eds.org wrote:
There are files missing from the pd/portaudio folder again. I guess new features of portaudio are being used.
../portaudio/pa_mac_core/pa_mac_core.c:61:25: pa_mac_core.h: No such file or directory ../portaudio/pa_mac_core/pa_mac_core.c:124:35: pa_mac_core_utilities.c: No such file or directory ../portaudio/pa_mac_core/pa_mac_core.c:127:34: ../pablio/ ringbuffer.c: No such file or directory
I propose that we import the whole portaudio source tree into CVS at pd/portaudio so that we don't have this problem again (since its happened before too). I'll happily do it if there are no objections.
Which version is the preferred version?
.hc
The arc of history bends towards justice. - Dr. Martin Luther King, Jr.
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev