forked from bartvdbraak/blender
Fix T49286: Compilation error with XCode 7.0
Weirdly enough, this version of XCode seems to have static_assert() even when NOT using C++11. This is totally weird and counter intuitive since static_assert() is supposed to be C++11 onlky feature. Can XCode stop using future, please? :)
This commit is contained in:
parent
7e7a9d146c
commit
18ae1504ea
@ -25,6 +25,10 @@ CCL_NAMESPACE_BEGIN
|
|||||||
#ifndef __KERNEL_GPU__
|
#ifndef __KERNEL_GPU__
|
||||||
# if (__cplusplus > 199711L) || (defined(_MSC_VER) && _MSC_VER >= 1800)
|
# if (__cplusplus > 199711L) || (defined(_MSC_VER) && _MSC_VER >= 1800)
|
||||||
/* C++11 has built-in static_assert() */
|
/* C++11 has built-in static_assert() */
|
||||||
|
# elif defined(static_assert)
|
||||||
|
/* Some platforms might have static_assert() defined even tho their
|
||||||
|
* C++ support wouldn't be declared to be C++11.
|
||||||
|
*/
|
||||||
# else /* C++11 or MSVC2015 */
|
# else /* C++11 or MSVC2015 */
|
||||||
template <bool Test> class StaticAssertFailure;
|
template <bool Test> class StaticAssertFailure;
|
||||||
template <> class StaticAssertFailure<true> {};
|
template <> class StaticAssertFailure<true> {};
|
||||||
|
Loading…
Reference in New Issue
Block a user