Yep, but this GCC is pretty old (4.2) and knows nothing about c++11, it kinda defeats the purpose.
I don't see any point in supporting OS X below Lion. Actually, we don't support 32-but builds (actually I'd like to provide such support, but it will involve a lot of mess with Ogre for example because Ogre assumes that 32-bit builds are always use Carbon, not Cocoa) on OS X, any Mac that can into 64-bit can upgrade to Lion.
And hey, we'll have 10.9 in month or two.
And yes, it's impossible to mix libstdc++ & libc++. For example, their std::string implementation details differ. So if you pass some string from OpenMW built against libc++ to library built against libstdc++, you'll get some undefined behaviour or just crash.
C++11
Re: C++11
Gentlemen, I finally managed to make C++11 build on OS X. Here's my branch with required changes: https://github.com/corristo/openmw/tree/osx-c%2B%2B11
Here's the diff: https://github.com/corristo/openmw/comm ... 28e214c1c0
Could you Windows and Linux guys check if this builds in C++11 mode?
Here's the diff: https://github.com/corristo/openmw/comm ... 28e214c1c0
Could you Windows and Linux guys check if this builds in C++11 mode?
Re: C++11
I am having major trouble here. Apparently the default boost install on Linux Mint 13 does not work with c++11. I manually installed boost 1.55, ended up in dependency hell and then after rebuilding the entire universe found out that the default build of 1.55 does not support c++11 either. Guess I could start from scratch again, this time with c++11 enabled.
The question here is as follows: Is that a general problem even for newer preinstalled boost packages on Linux? Or do they come with c++11 support enabled? If they don't then we need to do something different, because we can not require everyone to rebuild boost. The only problem seems to be the function copy_file from boost filesystem and we can probably work around that if necessary.
The question here is as follows: Is that a general problem even for newer preinstalled boost packages on Linux? Or do they come with c++11 support enabled? If they don't then we need to do something different, because we can not require everyone to rebuild boost. The only problem seems to be the function copy_file from boost filesystem and we can probably work around that if necessary.
Re: C++11
That's weird, both C++11 and non-C++11 linux builds of boost use one and the same libstdc++, I'm surprised that any rebuilding is required.
I had to rebuild all deps on mac only because non-C++11 builds used libstdc++ and C++11 is only possible with libc++. But that's not the case for Linux.
I had to rebuild all deps on mac only because non-C++11 builds used libstdc++ and C++11 is only possible with libc++. But that's not the case for Linux.
Re: C++11
Not sure if I have to do anything different to compile in C++11 mode, but your patch compiles & runs fine (I didn't change any of the dependencies, i.e. Ogre, Boost, etc). Having said that I didn't pay too much attention to whether there were any additional warnings (I usually get hundreds so I'm conditioned to ignore them)
I'm using VS2012 (Version 11.0.61030.00 Update 4). Windows 7 x64. Only test-built openmw x64 Release version.
EDIT: oops
I'm using VS2012 (Version 11.0.61030.00 Update 4). Windows 7 x64. Only test-built openmw x64 Release version.
EDIT: oops