DXSDK9.0 .... Reaction Engine compilation error
by Saurav Mohapatra · in General Game Discussion · 05/27/2003 (6:01 pm) · 4 replies
i just rebuilt my mahcine with XP Pro and DXSDK 9.0 Visual Studio 6.0 sp 5.0
and i rebuilt my RE SDK and got the following errors.. has anyone faced this before...
i have tried putting the RESDK/includes/d3d before the d3dsdk includes... but does not seem to affect anything
thanks in advance
and i rebuilt my RE SDK and got the following errors.. has anyone faced this before...
OS.cpp .\Includes\GFX.h(25) : error C2146: syntax error : missing ';' before identifier 'LP_RENDER_SURFACE' .\Includes\GFX.h(25) : fatal error C1004: unexpected end of file found Windows.cpp GFX_Device.cpp .\Includes\GFX.h(25) : error C2146: syntax error : missing ';' before identifier 'LP_RENDER_SURFACE' .\Includes\GFX.h(25) : fatal error C1004: unexpected end of file found GFX_FPS.cpp .\Includes\debug.h(86) : error C2061: syntax error : identifier 'LPDIRECTDRAW7' .\Includes\debug.h(87) : error C2061: syntax error : identifier 'LPDIRECT3D7' .\Includes\GFX.h(25) : error C2146: syntax error : missing ';' before identifier 'LP_RENDER_SURFACE' .\Includes\GFX.h(25) : fatal error C1004: unexpected end of file found
i have tried putting the RESDK/includes/d3d before the d3dsdk includes... but does not seem to affect anything
thanks in advance
About the author
#2
I used DX 9.0 to resolve a couple of bugs for Chris and even provided him a memory leak
dump that he was supposed to check into ;)
-Ron
05/27/2003 (6:33 pm)
Was about to say that I have no issues with RE and DX 9.0I used DX 9.0 to resolve a couple of bugs for Chris and even provided him a memory leak
dump that he was supposed to check into ;)
-Ron
#3
I think the memory leak errors you found are fixed now. Though I still don't see the errors. Ken Paulson found the same leaks. I was being a bit cavalier about gracefully closing down the examples on exit. The new AppDestroy should be used to clean up any allocated memory and it should get rid of these errors.
Can you verify that the example apps no longer have all the memory leaks... No guarantees I got them all though.
Chris
05/28/2003 (4:58 am)
RonI think the memory leak errors you found are fixed now. Though I still don't see the errors. Ken Paulson found the same leaks. I was being a bit cavalier about gracefully closing down the examples on exit. The new AppDestroy should be used to clean up any allocated memory and it should get rid of these errors.
Can you verify that the example apps no longer have all the memory leaks... No guarantees I got them all though.
Chris
Torque Owner Saurav Mohapatra