Yes - I have the editor and Teapot Wars up and running using Visual Studio 2010, the June 2010 release of DirectX, and even Boost 1.45.
Here's what I need to do next:
1. Create 2010 specific versions of the solution files and put them up alongside the ones that work now for 2005 and 2008.
2. Make sure 2005 still works (hopefully if it does 2008 won't be a problem!)
3. Check in everything into the Google test branch - including an additional 3rdParty.zip with precompiled Boost 1.45 libraries.
4. Let you people wail on it a bit to see if I've busted anything.
We're getting there.
For those that want to fix things themselves, I had to do two things to get everything happy:
1. Grab the new Boost and compile the libraries.
2. Change the V(x) macros in DXUT to VVV(x) - there was a template in Boost 1.45 thread libraries that flipped out when I broght them together. Easiest solution for me was to just rename the offending macro, which should NEVER have been named "V(x)" anyway! Too likely some conflict will happen, as it did.
Here's what I need to do next:
1. Create 2010 specific versions of the solution files and put them up alongside the ones that work now for 2005 and 2008.
2. Make sure 2005 still works (hopefully if it does 2008 won't be a problem!)
3. Check in everything into the Google test branch - including an additional 3rdParty.zip with precompiled Boost 1.45 libraries.
4. Let you people wail on it a bit to see if I've busted anything.
We're getting there.
For those that want to fix things themselves, I had to do two things to get everything happy:
1. Grab the new Boost and compile the libraries.
2. Change the V(x) macros in DXUT to VVV(x) - there was a template in Boost 1.45 thread libraries that flipped out when I broght them together. Easiest solution for me was to just rename the offending macro, which should NEVER have been named "V(x)" anyway! Too likely some conflict will happen, as it did.
Mr.Mike
Author, Programmer, Brewer, Patriot
Author, Programmer, Brewer, Patriot