summaryrefslogtreecommitdiff
path: root/cmake/check_compiler_flag.cmake
Commit message (Collapse)AuthorAgeFilesLines
* Merge 10.1 into 10.2Marko Mäkelä2019-06-121-1/+2
|\
| * MDEV-17103 MY_CHECK_{C,CXX}_COMPILER_FLAG do not work on with localized gccVladislav Vaintroub2019-06-051-1/+2
| | | | | | | | | | | | messages Force LANG=C for MY_CHECK_{C,CXX}_COMPILER_FLAG
* | Merge branch 'github/10.1' into 10.2Sergei Golubchik2018-02-061-7/+7
|\ \ | |/
| * correctly detect unsupported compiler flagsSergei Golubchik2018-02-061-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | Merge branch '10.1' into 10.2Sergei Golubchik2016-06-301-3/+3
|\ \ | |/
| * Merge branch '10.0' into 10.1Sergei Golubchik2016-06-281-3/+3
| |
* | cmake: rename symbols used internally by check_compiler_flag.cmakeSergei Golubchik2015-11-231-3/+3
|/ | | | | | | | (that is MY_CHECK_C_COMPILER_FLAG, MY_CHECK_CXX_COMPILER_FLAG, MY_CHECK_AND_SET_COMPILER_FLAG) This is to have a clear "internal" name prefix and to avoid mixing them with hand-named symbols
* cmake: always use the same function to test for compiler flagsSergei Golubchik2015-09-041-5/+9
| | | | | | | 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.
* smarter MY_CHECK_AND_SET_COMPILER_FLAGSergei Golubchik2015-04-101-10/+10
| | | | | | 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.
* MY_CHECK_AND_SET_COMPILER_FLAG changesAlexey Botchkov2015-03-111-0/+1
| | | | | * watch for "redefined macro" warning * don't enable -D_FORTIFY_SOURCE=2 in debug builds (it requires -O)
* cmake cleanup: use MY_CHECK_AND_SET_COMPILER_FLAG.Sergei Golubchik2014-06-261-0/+51
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.
View Lorry Controller Status