[wdmaudiodev] Re: Trouble building DirectKS sample
- From: "Martin Puryear" <martinp@xxxxxxxxxxxxxxxxxxxxx>
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Thu, 29 May 2003 21:41:21 -0700
If multiple parties are hitting this, it probably behooves Microsoft to =
update the sample code. =20
So, if someone wants to contribute to the greater good and send me the =
tweaks they had to do to make this build cleanly, I can incorporate this =
into the master copy. It actually takes a while to make it through our =
web editors etc., so it wouldn't show up on the web site for a number of =
weeks or months, but it would be best for us to fix this up if it is =
wasting people's time.
Martin Puryear
Development Manager
Microsoft Windows Audio/Video Platform
This posting is provided "AS IS" with no warranties, and confers no =
rights.
Ce message est fourni en l'=E9tat, sans garantie d'aucune sorte, et ne =
vous conf=E8re aucun droit. Vous assumez tous les risques li=E9s =E0 son =
utilisation.
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx =
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of wade dawson
Sent: Wednesday, May 21, 2003 6:59 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Trouble building DirectKS sample
This sample, KsDirect builds using vc 7 (.net) and the latest directx =
sdk. It has a debug macro which uses the __FUNCTION__ keyword built-in =
to vc7. #define __FUNCTION__ to some string to build it on vc6.
Most importantly, I found the order of include directories to be =
important:
=20
/dxsdk/include
.../vc98/include
.../vc98/mfc/include
.../vc98/atl/include
/winddk/2600.1106/inc/wxp
=20
=20
=20
=20
Andy Voelkel <andy@xxxxxxxxxxxx> wrote:
> I had this problem too...I beleive I solved it by commented the line :
> //#define WINVER 0x0501
> in kssample.h.
> Try it. If it doesn't work set WINVER at 0x0400.
But don't we want the latest OS features (assuming that we are willing =
to limit our target machines to Win2000 - or even Win98 - and later)? I =
still find that part of the error message to be strange.
> I also had the undeclared identifiers. I don't remember very well but=20
> I think I had to manually include headers supplying the definitions=20
> (Maybe #include )....
Good memory. The question is, why was the include of winioctl.h missing?
How could the author have ever built the project?
Scratching my head ...
Andy
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=3Dsubscribe
Unsubscribe: =
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=3Dunsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.de/
---------------------------------
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: =
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=3Dsubscribe
Unsubscribe: =
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=3Dunsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.de/
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.de/
Other related posts:
