hi –
I’ll try to explain the problem with vs 2008 as best I can…
first, MSoft makes it impossible to compile libraries that work across versions of their IDE. Why? I have no idea.
some info:
http://brianstewart.wordpress.com/2008/-…-udio-2008/
http://social.msdn.microsoft.com/forums-…-f39ae6e69/
http://stackoverflow.com/questions/4933-…-ry-linking
second, when we made the 0.05 package for VS 2005, we made it with a specific idea in mind, which was to have the same libraries for debug and release. The reason is that the properties panel in VS is very fidgety, and if you add a library under “all” targets and you have different debug and release libraries, it winds up overwriting the debug and release ones. This was a bg problem as people started to use addons, so with vs 2005 we acheived that.
third, with VS 2008, there are bigger problems. you can’t compile debug libraries that work in release, or release libraries that work in debug, primarily because of new things they are doing, like SECURE_SCL settings, etc
http://connect.microsoft.com/VisualStud-…-kID=352481
I haven’t for example, been able to make a rtAudio library (one) that works across debug and release in 2008. I do have both debug and release versions compiled and I will put them online. Also, if I have a free moment, I can make a minimal OF package for 2008 – maybe not every app, but a starting point for a 2008 release where debug and release are working.
One thing that’ hard for us right now, is creating packages for each compiler, especially based on quirks like this… I keep hitting my head against the wall with VS issues, they seem to make it very hard to do simple stuff. Likely for 0.06 we will just support 2008, so that it’s easier to stay up to date with all the weird issues, etc.
sorry about the frustration!
take care,
zach