Cannot activate C++11 with libc++ about cocos2d-x

[alvin777]

I also run into this issue. To analyse it I run Product -> Generate Output -> Preprocessed File to get a preprocessor output (gcc/clang -E option). Quick glance revealed that cocos2dx uthash.h includes <inttypes.h> in the cocos2d namespace which ruins stdint.h inclusion. _UINT8_T macro is set, but uint8_t type is defined in cocos2d namespace and not in global.

I dirtyfixed it by moving #include <inttypes.h> line in uthash.h to the beginning of the file.

[Klaim]

Works for me too, but I guess it needs to be checked on other platforms than IOS

[kagakuninja]

We can use macros to make the static_casts only happen for C++11, if people are worried about other platforms. Can we get this done?

Could you not just set all those -1s to UINT32_MAX? That might be faster and we wouldn't need to care about the platform.

[stnguyen]

This works for me with XCode 4.4, cocos2d-x 2.0:

1. Select your Target > Build Settings > All
2. Find C++ Language Dialect, select C++11 [-std=c++11]
3. Find C++ Standard Library, select libc++ (LLVM C++ standard library with C++11 support)

[kagakuninja]

Just a warning, if you compile with -std=c++11, then your app will require iOS version 5 or above. I use -std=gnu++11. I had to fix some errors due to bad casts.

[donaldalanmorrison]

This issue can be closed as "not a cocos2d-x issue" or "as designed".

XCode 4.5 does not fully support c++11:

http://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/WhatsNewXcode/Articles/xcode_4_5.html#//apple_ref/doc/uid/TP40012559-SW1

@minggo @dumganhar @walzer :-)

[Ryandev]

@donaldalanmorrison Nothing in cocos2dx uses anything new in the c++11 standard. So it should still compile against it.

For myself the errors occurring where:
'Unknown type name 'class'; did you mean 'Class'?'

This issue is to do with Xcode->Build Settings->Compile Sources As="According to File Type"

When compiling cocos2dx there is a mix of objective-c & c++. Xcode does struggle to differentiate between the two types. The solution is to wrap each header in a ifdef for that platform. If compiling CCSprite.h wrap the header in:
#ifdef __cplusplus
CCSPRITE HEADER
#endif /* __cplusplus */

the same too for any objective-c files (OBJC)

After the above, Xcode no longer confuses objc with c++ & the cocos2dx source compiles against c++11.

An easy win that won't cause any complications on other platforms I believe.

As for why to bother doing it: I'm new to C++ & using the latest standard does help make things easier.

Cheers,
Ryan

[godyZ]

@Klaim Please, could you open a bug in redmine in future? We are in process of migrating all the issues to redmine and github issue won't be available after August.

[Klaim]

@godyZ Noted!