From: J. P. <ja...@si...> - 2004-03-09 20:30:40
|
Matt Homes <cal...@ho...> wrote: > Actually, with DirectX, you always link to a particular version. For > instance, you tell VC++ to link to d3d8.lib instead of d3d9.lib if you > want to use D3D8 interfaces. How is this any different? When MS release= s > DX10, we will get Microsoft.DirectX.Direct3D version 1.1000.0 or > whatever they call it. But if I want to use the old DirectX 9 > interfaces, I will have to reference back to the old managed DX9 > assemblies. I highly doubt MS is going to stick all of the code in one > big assembly, or break DX9 backward compat. So I really don't see the > problem with referencing a particular version of the D3D9 assemblies? Well, there is a way to find out, but I don't have a clean machine to try it on. Starting with a DX9-free machine, install the "DX9 Summer Update" and see if includes two version of Microsoft.DirectX (1.0.900.0 and 1.0.1901.0). If it does, then you're right, there is no issue. If it doesn't, then hardcoding a version number will cause issues as people migrate (or don't migrate) up to newer versions. Personally, unless I use a feature specific to a particular version I'd rather work with whatever is available. But no worries, premake works either way. Jason |