Remove QT_HAS_FOO() wrapper macros for __has_foo()
Using wrappers for these macros is problematic when for example passing the -frewrite-includes flag to preprocess sources before shipping off to distcc or Icecream. It will also start producing warnings when compilers implement http://eel.is/c++draft/cpp.cond#7.sentence-2. See for example https://reviews.llvm.org/D49091 Now that all uses of the macros are gone, we can follow up c3bd5ffdc8a3b459f18ba6e35fca93e29f3b0ab0 and remove the wrappers. Change-Id: I764aea17dcdabd420097a7f4bc0b987a53a345eb Reviewed-by: Marc Mutz <marc.mutz@qt.io>
This commit is contained in:
parent
23be657dda
commit
71f35d6057
@ -445,14 +445,6 @@
|
||||
# define __has_include_next(x) 0
|
||||
#endif
|
||||
|
||||
// Kept around until all submodules have transitioned
|
||||
#define QT_HAS_BUILTIN(x) __has_builtin(x)
|
||||
#define QT_HAS_FEATURE(x) __has_feature(x)
|
||||
#define QT_HAS_ATTRIBUTE(x) __has_attribute(x)
|
||||
#define QT_HAS_CPP_ATTRIBUTE(x) __has_cpp_attribute(x)
|
||||
#define QT_HAS_INCLUDE(x) __has_include(x)
|
||||
#define QT_HAS_INCLUDE_NEXT(x) __has_include_next(x)
|
||||
|
||||
#ifdef __cplusplus
|
||||
# if __has_include(<version>) /* remove this check once Integrity, QNX have caught up */
|
||||
# include <version>
|
||||
|
Loading…
x
Reference in New Issue
Block a user