[Portaudio] Compilation Instructions for Windows

[c319chris at aol.com]

All I know is that I couldn't get a successful compilation without those steps. I can go back and undo them and see if it still compiles.

 

 

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



Chris,
 
I checked, and I have no references to theDirectX SDK in my project.
 
dsound.h and dsconf.h are located in theWindows 7 SDK (for my system).  When installing this SDK, it automaticallyregistered itself with VC++ Express.  So no, there were no extra stepsrequired to ensure the appropriate headers and libraries for DirectSound wereavailable for compiling.
 
Perhaps your instructions are slightlydated?  I do know there was some restructuring of the project awhile ago-and older compile guides may not be relevant.
 
-Reid-
W0CNN
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 3:34AM
To: portaudio at music.columbia.edu
Subject: Re: [Portaudio]Compilation Instructions for Windows

 
>> Instead, you should add the pathto the DX SDK includes directory to your VS project (during some of the otherproject settings

tasks below in step 8, or perhaps as aseparate step).

Could you or someone else please provide exact, detailed instructions on how todo this? I don't mean to lecture but the lack of specificity is the majordownfall of the existing documentation.





 
_______________________________________________

Portaudio mailing list

Portaudio at music.columbia.edu

http://music.columbia.edu/mailman/listinfo/portaudio


 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://music.columbia.edu/pipermail/portaudio/attachments/20100709/37397e59/attachment.html>