Sign in to follow this  
WuTz

It wants the Debug DLLs in release builds!? wtf?

Recommended Posts

Hi! I did a (fake)release build, but the program still wants d3dx10d_42.dll and d3dx9d_42.dll! I made this fake-release, because my engine isn't working with code optimizations. Im not linking to the debug libs anymore, I changed the Runtime-lib and I changed the PreProcDeffines. And everything works good on other PCs, when I ship it with both Debug-DLLs from directX! (Just to some friends) And I have no idea why. :(

Share this post


Link to post
Share on other sites
I said that already.

[quote="WuTz"]
Im not linking to the debug libs anymore
[/quote]

I link to: dxerr.lib dxguid.lib d3dx9.lib d3d9.lib d3dx10.lib winmm.lib comctl32.lib

No "d"...

Share this post


Link to post
Share on other sites
Probably not the solution, but do you still pass the D3D10_CREATE_DEVICE_DEBUG flag to D3D10CreateDeviceAndSwapChain()? Or D3D10_SHADER_DEBUG for D3DX10CreateEffectFromFile()?

Share this post


Link to post
Share on other sites
If you have the SDK install it usually installs (at least the DX9 SDK) a control panel app that controls what version of the runtime to use. I don't remember the default settings but you can try and see if its set to use the Debug runtime. Most end-users won't be affected by this since the redistributable doesn't include the control panel app and the Release runtime is the default.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this