Visual Studio 2012 RC

[TheEnigmist]

I see that M$ releases VS2012! Now i've some question about:
How much of you use VS2012 RC?
How is C++11 support?
Can i still use sfml2 under VS2012?

[Acrobat]

even on VS 2010 most C++11 features supported, sfml2 on 2012, why not ?

[TheEnigmist]

even on VS 2010 most C++11 features supported, sfml2 on 2012, why not ?

I'm downloading 2012, but have i to build with Cmake SFML2 for better support of SFML in VS2012?

[Nexus]

M$

Please write Microsoft or MS, if you want to be taken seriously.

even on VS 2010 most C++11 features supported

No, major C++11 features such as variadic templates, initializer lists and uniform initialization are still not supported. In fact, VS 2012 RC adds only few language features. However, they implement the whole C++11 standard library, which I find very nice.

I'm downloading 2012, but have i to build with Cmake SFML2 for better support of SFML in VS2012?

Yes, the precompiled libraries are probably not compatible.

[TheEnigmist]

Please write Microsoft or MS, if you want to be taken seriously.

Yes, sorry for this!

Yes, the precompiled libraries are probably not compatible.

Uhm, cmake can build for Visual Studio 11... is that the right build,isn't it?
(VS11 = visual studio 2012 if i'm right)

[Nexus]

Yes, I would try VS11. The CMake generator was conceived for VS11 Developer Preview or Beta though.

[TheEnigmist]

Yes, I would try VS11. The CMake generator was conceived for VS11 Developer Preview or Beta though.

Ok, if it won't work how can i use SFML2 under VS11?

[TheEnigmist]

Check for working C compiler using: Visual Studio 11
Check for working C compiler using: Visual Studio 11 -- broken
CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:52 (MESSAGE):
  The C compiler "cl" is not able to compile a simple test program.

Cmake can't build SFML for VS11 RC! There is a way to build it manually?

[jDralliam]

Did you launch cmake from the Visual command line (otherwise environment variables are not correctly set and cmake can't find cl) ?

[Laurent]

VC++ 10 binaries are compatible with VC++ 11, you don't need to recompile SFML;

And VC++ 11 (compiler) = VS 2012 (IDE). There's no Visual Studio 2011.

[TheEnigmist]

VC++ 10 binaries are compatible with VC++ 11, you don't need to recompile SFML;

And VC++ 11 (compiler) = VS 2012 (IDE). There's no Visual Studio 2011.

Nice...
Have i to compile with cmake to get 64bit version for VS?

[Laurent]

Yes.

[Acrobat]

No, major C++11 features such as variadic templates, initializer lists and uniform initialization are still not supported. In fact, VS 2012 RC adds only few language features. However, they implement the whole C++11 standard library, which I find very nice.

Other compilers are still far behind. We are developing a game on MacOS and windows at the same time, and it was a bad news that xcode still not support lambdas, begin(), end(), (even enum forward declaration  ) etc.
At the moment we only use auto keyword. If you are developing only under Windows - no problem, else it's not a good idea to use whole C++11 (or you can try gcc Macports, but it's not official).

[Silvah]

Other compilers are still far behind. We are developing a game on MacOS and windows at the same time, and it was a bad news that xcode still not support lambdas, begin(), end(), (even enum forward declaration  ) etc.

Or just forget llvm-gcc, it uses an old GCC frontend (4.2) and it's not developed anymore. Use Clang or a modern GCC with DragonEgg (or without it, if you don't want LLVM backend) instead. The current versions – Clang 3.1 and GCC 4.7 – have almost complete C++11 support.

If you are developing only under Windows - no problem, else it's not a good idea to use whole C++11 (or you can try gcc Macports, but it's not official).

Actually, Windows has the poorest support for C++11 of the three major platforms, as the official compiler, even in the upcoming release, has a lousy support for it.

[Klaim]

Yes but it have all the libraries, that is still an advantage. The problem is more that all compiler don't match on features.


On Mac, XCode comes with the a verison of Clang that is not the same as the last one. So you have to add the last version of clang as a plugin (I didn't try but someone explained to me how to do this on the clang mailing list) or you wait for the next XCode update...