Mirrors
/
mariadb
mirror of https://github.com/MariaDB/server
3
0
Fork 0
Code Releases Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
177971 Commits
3333 Branches
1099 Tags
1.3 GiB
Tree: 0c7c61019d
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '0c7c61019d'
${ noResults }
mariadb/cmake/check_compiler_flag.cmake

57 lines
2.1 KiB
Raw Normal View History

cmake cleanup: use MY_CHECK_AND_SET_COMPILER_FLAG. move MY_CHECK_C_COMPILER_FLAG and MY_CHECK_CXX_COMPILER_FLAG to a separate file, introduce MY_CHECK_AND_SET_COMPILER_FLAG, use it where possible.
12 years ago
​
​
​
​
​
​
​
​
​
​
cmake: always use the same function to test for compiler flags Fix all cmake tests (including plugin) to use MY_CHECK_AND_SET_COMPILER_FLAG. And fix that function to be compatible with cmake 3.0. This way flag checks are correctly cached (even in cmake 3.0) and properly reused.
10 years ago
MY_CHECK_AND_SET_COMPILER_FLAG changes * watch for "redefined macro" warning * don't enable -D_FORTIFY_SOURCE=2 in debug builds (it requires -O)
11 years ago
cmake cleanup: use MY_CHECK_AND_SET_COMPILER_FLAG. move MY_CHECK_C_COMPILER_FLAG and MY_CHECK_CXX_COMPILER_FLAG to a separate file, introduce MY_CHECK_AND_SET_COMPILER_FLAG, use it where possible.
12 years ago
​
MDEV-17103 MY_CHECK_{C,CXX}_COMPILER_FLAG do not work on with localized gcc messages Force LANG=C for MY_CHECK_{C,CXX}_COMPILER_FLAG
7 years ago
​
cmake: always use the same function to test for compiler flags Fix all cmake tests (including plugin) to use MY_CHECK_AND_SET_COMPILER_FLAG. And fix that function to be compatible with cmake 3.0. This way flag checks are correctly cached (even in cmake 3.0) and properly reused.
10 years ago
Merge branch '10.0' into 10.1
10 years ago
cmake cleanup: use MY_CHECK_AND_SET_COMPILER_FLAG. move MY_CHECK_C_COMPILER_FLAG and MY_CHECK_CXX_COMPILER_FLAG to a separate file, introduce MY_CHECK_AND_SET_COMPILER_FLAG, use it where possible.
12 years ago
​
​
​
​
​
​
cmake: always use the same function to test for compiler flags Fix all cmake tests (including plugin) to use MY_CHECK_AND_SET_COMPILER_FLAG. And fix that function to be compatible with cmake 3.0. This way flag checks are correctly cached (even in cmake 3.0) and properly reused.
10 years ago
Merge branch '10.0' into 10.1
10 years ago
cmake cleanup: use MY_CHECK_AND_SET_COMPILER_FLAG. move MY_CHECK_C_COMPILER_FLAG and MY_CHECK_CXX_COMPILER_FLAG to a separate file, introduce MY_CHECK_AND_SET_COMPILER_FLAG, use it where possible.
12 years ago
​
​
​
​
​
​
correctly detect unsupported compiler flags in gcc `-Wno-unsupported-something` will not be an error or even a warning, so cmake will think the flag is supported. But if there's any other warning during compilation, for any reason, unknown option will be a warning too. Or an error when -Werror, even if that "other warning" would not be an error on itself. So we need to detect whether `-Wno-unsupported-something` is *really* supported. Luckily, `-Wunsupported-something` will always fail with an error. So, whenever there's a need to detect if -Wno-something is supported, test -Wsomething instead.
8 years ago
cmake cleanup: use MY_CHECK_AND_SET_COMPILER_FLAG. move MY_CHECK_C_COMPILER_FLAG and MY_CHECK_CXX_COMPILER_FLAG to a separate file, introduce MY_CHECK_AND_SET_COMPILER_FLAG, use it where possible.
12 years ago
​
​
​
​
correctly detect unsupported compiler flags in gcc `-Wno-unsupported-something` will not be an error or even a warning, so cmake will think the flag is supported. But if there's any other warning during compilation, for any reason, unknown option will be a warning too. Or an error when -Werror, even if that "other warning" would not be an error on itself. So we need to detect whether `-Wno-unsupported-something` is *really* supported. Luckily, `-Wunsupported-something` will always fail with an error. So, whenever there's a need to detect if -Wno-something is supported, test -Wsomething instead.
8 years ago
​
​
​
smarter MY_CHECK_AND_SET_COMPILER_FLAG If a flag is supported only for C or C++ - add it to the corresponding compiler option list. Old behavior was to add always to both, but only if supported in both.
11 years ago
cmake: always use the same function to test for compiler flags Fix all cmake tests (including plugin) to use MY_CHECK_AND_SET_COMPILER_FLAG. And fix that function to be compatible with cmake 3.0. This way flag checks are correctly cached (even in cmake 3.0) and properly reused.
10 years ago
smarter MY_CHECK_AND_SET_COMPILER_FLAG If a flag is supported only for C or C++ - add it to the corresponding compiler option list. Old behavior was to add always to both, but only if supported in both.
11 years ago
​
correctly detect unsupported compiler flags in gcc `-Wno-unsupported-something` will not be an error or even a warning, so cmake will think the flag is supported. But if there's any other warning during compilation, for any reason, unknown option will be a warning too. Or an error when -Werror, even if that "other warning" would not be an error on itself. So we need to detect whether `-Wno-unsupported-something` is *really* supported. Luckily, `-Wunsupported-something` will always fail with an error. So, whenever there's a need to detect if -Wno-something is supported, test -Wsomething instead.
8 years ago
smarter MY_CHECK_AND_SET_COMPILER_FLAG If a flag is supported only for C or C++ - add it to the corresponding compiler option list. Old behavior was to add always to both, but only if supported in both.
11 years ago
​
correctly detect unsupported compiler flags in gcc `-Wno-unsupported-something` will not be an error or even a warning, so cmake will think the flag is supported. But if there's any other warning during compilation, for any reason, unknown option will be a warning too. Or an error when -Werror, even if that "other warning" would not be an error on itself. So we need to detect whether `-Wno-unsupported-something` is *really* supported. Luckily, `-Wunsupported-something` will always fail with an error. So, whenever there's a need to detect if -Wno-something is supported, test -Wsomething instead.
8 years ago
smarter MY_CHECK_AND_SET_COMPILER_FLAG If a flag is supported only for C or C++ - add it to the corresponding compiler option list. Old behavior was to add always to both, but only if supported in both.
11 years ago
cmake cleanup: use MY_CHECK_AND_SET_COMPILER_FLAG. move MY_CHECK_C_COMPILER_FLAG and MY_CHECK_CXX_COMPILER_FLAG to a separate file, introduce MY_CHECK_AND_SET_COMPILER_FLAG, use it where possible.
12 years ago
smarter MY_CHECK_AND_SET_COMPILER_FLAG If a flag is supported only for C or C++ - add it to the corresponding compiler option list. Old behavior was to add always to both, but only if supported in both.
11 years ago
cmake cleanup: use MY_CHECK_AND_SET_COMPILER_FLAG. move MY_CHECK_C_COMPILER_FLAG and MY_CHECK_CXX_COMPILER_FLAG to a separate file, introduce MY_CHECK_AND_SET_COMPILER_FLAG, use it where possible.
12 years ago
  1. include(CheckCSourceCompiles)
  2. include(CheckCXXSourceCompiles)
  3. # We need some extra FAIL_REGEX patterns
  4. # Note that CHECK_C_SOURCE_COMPILES is a misnomer, it will also link.
  5. SET(fail_patterns
  6. FAIL_REGEX "argument unused during compilation"
  7. FAIL_REGEX "unsupported .*option"
  8. FAIL_REGEX "unknown .*option"
  9. FAIL_REGEX "unrecognized .*option"
  10. FAIL_REGEX "ignoring unknown option"
  11. FAIL_REGEX "warning:.*ignored"
  12. FAIL_REGEX "warning:.*is valid for.*but not for"
  13. FAIL_REGEX "warning:.*redefined"
  14. FAIL_REGEX "[Ww]arning: [Oo]ption"
  15. )
  16. #The regex patterns above are not localized, thus LANG=C
  17. SET(ENV{LANG} C)
  18. MACRO (MY_CHECK_C_COMPILER_FLAG flag)
  19. STRING(REGEX REPLACE "[-,= +]" "_" result "HAVE_C_${flag}")
  20. SET(SAVE_CMAKE_REQUIRED_FLAGS "${CMAKE_REQUIRED_FLAGS}")
  21. SET(CMAKE_REQUIRED_FLAGS "${CMAKE_REQUIRED_FLAGS} ${flag}")
  22. CHECK_C_SOURCE_COMPILES("int main(void) { return 0; }" ${result}
  23. ${fail_patterns})
  24. SET(CMAKE_REQUIRED_FLAGS "${SAVE_CMAKE_REQUIRED_FLAGS}")
  25. ENDMACRO()
  27. MACRO (MY_CHECK_CXX_COMPILER_FLAG flag)
  28. STRING(REGEX REPLACE "[-,= +]" "_" result "HAVE_CXX_${flag}")
  29. SET(SAVE_CMAKE_REQUIRED_FLAGS "${CMAKE_REQUIRED_FLAGS}")
  30. SET(CMAKE_REQUIRED_FLAGS "${CMAKE_REQUIRED_FLAGS} ${flag}")
  31. CHECK_CXX_SOURCE_COMPILES("int main(void) { return 0; }" ${result}
  32. ${fail_patterns})
  33. SET(CMAKE_REQUIRED_FLAGS "${SAVE_CMAKE_REQUIRED_FLAGS}")
  34. ENDMACRO()
  36. FUNCTION(MY_CHECK_AND_SET_COMPILER_FLAG flag_to_set)
  37. # At the moment this is gcc-only.
  38. # Let's avoid expensive compiler tests on Windows:
  39. IF(WIN32)
  40. RETURN()
  41. ENDIF()
  42. STRING(REGEX REPLACE "^-Wno-" "-W" flag_to_check ${flag_to_set})
  43. MY_CHECK_C_COMPILER_FLAG(${flag_to_check})
  44. MY_CHECK_CXX_COMPILER_FLAG(${flag_to_check})
  45. STRING(REGEX REPLACE "[-,= +]" "_" result "${flag_to_check}")
  46. FOREACH(lang C CXX)
  47. IF (HAVE_${lang}_${result})
  48. IF(ARGN)
  49. FOREACH(type ${ARGN})
  50. SET(CMAKE_${lang}_FLAGS_${type} "${CMAKE_${lang}_FLAGS_${type}} ${flag_to_set}" PARENT_SCOPE)
  51. ENDFOREACH()
  52. ELSE()
  53. SET(CMAKE_${lang}_FLAGS "${CMAKE_${lang}_FLAGS} ${flag_to_set}" PARENT_SCOPE)
  54. ENDIF()
  55. ENDIF()
  56. ENDFOREACH()
  57. ENDFUNCTION()