| |
| |
| |
|
Comments:
<0> Both of my systems have DirectX 9.0c (4.09.0000.0904) according to dxdiag.exe. One system is running win2k and the other is running winxp. When I compile a simple application (just loads and displays a jpg file as a texture) on windows XP and run it on windows 2000 I get an error regarding missing d3dx9_32.dll on the windows XP system. If I compile on windows 2000 I get an error regarding missing d3dx9_25.dll on the windows XP system. Any
<0> err d3dx9_32.dll is when compiled on XP, but run on 2k. d3dx9_25.dll is when compiled on 2k, but run on XP.
<1> it's two different DXSDK's
<1> just copy it over and it'll work
<0> just into the application dir?
<1> sure
<0> is it possible to use a newer SDK (dec 2006) that when compiled will only make use of older dlls?
<1> no
<1> and the code reacts differently
<1> so you wouldn't want to anyways
<1> but you can just have the dll alongside your application, or point to the page to download it
<0> if i compile with a new SDK, but have an older version of directX redist installed will it cause a problem? should i just install the redist that matches my SDK along with my application?
<1> the runtime hasn't really changed
<1> as long as they're both 9.0c it should work
<1> the redist has the dll in it too, possibly
<2> Asmodee`, you want the web setup
<2> it'll download all missing d3dx9 dlls
<2> Asmodee`, http://www.microsoft.com/downloads/details.aspx?familyid=2DA43D38-DB71-4C1B-BC6A-9B6652CD92A3&displaylang=en
<2> that tool will always make it up to date
<3> do you guys know how to compile a dx9 application on the new sdk?
<3> crap, its always those precompiled header's fault >:(
Return to
#directx
or
Go to some related
logs:
#beginner
schokira
#c
#politics
#freebsd
goodfella efnet
#networking
efnet QUOTE PONG
#freebsd
abaout limewire
|
|