Skip to main content

Topic: Visual Studio 2012 support? (Read 2304 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • hymerman
  • [*][*]
Visual Studio 2012 support?
I've grown quite fond of the new C++11 features provided by the VC11 compiler and standard library, so it makes me a bit sad to go back to VC10 when developing foobar components. Is there any intention to update the API to VC11 now that Visual Studio 2012 has been released?

  • Zao
  • [*][*][*][*][*]
  • Developer (Donating)
Visual Studio 2012 support?
Reply #1
The SDK builds just fine on VC11 with some minor patches to PFCv1.

If I recall correctly, you need to make a protected copy-assignment operator declaration in list_base_t, as the templated copy-assignment operator does not inhibit the synthesised copy-assignment operator which fails due to the copy-assignment operator in list_base_const_t being private, for good reason.

Note that the currently released VC11 versions prevent you from targetting Windows XP, so be aware of this if you've got users on that god-forsaken OS.
Zao shang yong zao nong zao rang zao ren zao.
To, early in the morning, use a chisel to build a bathtub makes impatient people hot-tempered.

  • kode54
  • [*][*][*][*][*]
  • Administrator
Visual Studio 2012 support?
Reply #2
I don't recall making that particular change to PFC to compile it with VC11, so your mileage may vary.

  • hymerman
  • [*][*]
Visual Studio 2012 support?
Reply #3
Ah, I assumed the C++ runtime version for component dlls would have to match that of foobar, but I guess since we build the SDK separately it doesn't matter. Cool, I'll give it a go, thanks

(VC11 project files would be nice in the next SDK release though)

  • kode54
  • [*][*][*][*][*]
  • Administrator
Visual Studio 2012 support?
Reply #4
All the right functions are either class interfaces or virtualized, so cross-runtime issues are handled. It's also why VC9 components still work.