[Portaudio] Compilation Instructions for Windows

c319chris at aol.com c319chris at aol.com
Sat Jul 10 00:14:55 EDT 2010

I don't use Visual Studio, I use Visual C++ 2008 Express. Wonder if that makes a difference.



-----Original Message-----
From: Reid Bishop <rbish at attglobal.net>
To: 'Portaudio Mailing List' <portaudio at music.columbia.edu>
Sent: Fri, Jul 9, 2010 8:47 pm
Subject: Re: [Portaudio] Compilation Instructions for Windows

I guess that is the rub… when usingVisual Studio 2008, if the user downloads the Vista SDK or Windows 7 SDK (note,NOT the DirectSound SDK, as there is no such SDK that I am aware of), thenVisual Studio is automatically made “aware” of the SDK and allinclude and library paths are automatically provisioned within Visual Studio. There is no configuration change that needs to be made by the user- VisualStudio takes care of it.  To be honest, I can’t even find wherethese includes and libraries are configured for Visual Studio- it’s notreadily apparent.
CNNSDR Development

From:portaudio-bounces at music.columbia.edu[mailto:portaudio-bounces at music.columbia.edu] OnBehalf Of c319chris at aol.com
Sent: Friday, July 09, 2010 7:37PM
To: portaudio at music.columbia.edu
Subject: Re: [Portaudio]Compilation Instructions for Windows


"If you installed the DirectSoundSDK then the DS libraries and header files should be found automatically byVisual Studio. But if you get an error about a missing dsound.h header filethen you can declare the paths by hand by ..." 


Phil or anyone -

We need to fill in the blank here. How exactly does one declare these paths?



Portaudio mailing list

Portaudio at music.columbia.edu


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://music.columbia.edu/pipermail/portaudio/attachments/20100710/caf0107e/attachment-0001.html>

More information about the Portaudio mailing list