Download-Tools/mkvtoolnix
1
0
Fork 0
mirror of https://gitlab.com/mbunkus/mkvtoolnix.git synced 2024-12-28 22:05:03 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
f1b2032c79
mkvtoolnix/ac/compiler_flags.m4

44 lines
1.3 KiB
Plaintext
Raw Normal View History

build system: move compiler warning flag checks to their own file
2013-10-26 10:03:20 +00:00
QUNUSED_ARGUMENTS=""
WNO_SELF_ASSIGN=""
WNO_MISMATCHED_TAGS=""
WLOGICAL_OP=""
if test x"$ac_cv_compiler_is_clang" = xyes; then
QUNUSED_ARGUMENTS="-Qunused-arguments"
WNO_SELF_ASSIGN="-Wno-self-assign"
WNO_MISMATCHED_TAGS="-Wno-mismatched-tags"
build system: enable gcc's stack protection Implements #1370.
2015-08-11 13:02:58 +00:00
FSTACK_PROTECTOR=""
build system: add -Wlogical-op warning flag for gcc 4.8.x
2013-10-26 10:12:24 +00:00
build system: check for and turn off some new warnings from clang++ 3.6 These warnings include -Winconsistent-missing-override and -Wpotentially-evaluated-expression which are both triggered by code out of my control (Qt and wxWidgets).
2015-03-25 16:51:30 +00:00
ac_save_CXXFLAGS="$CXXFLAGS"
AC_LANG_PUSH(C++)
CXXFLAGS="$ac_save_CXXFLAGS -Werror -Wno-inconsistent-missing-override"
AC_TRY_COMPILE([],[],[ WNO_INCONSISTENT_MISSING_OVERRIDE="-Wno-inconsistent-missing-override" ],[])
CXXFLAGS="$ac_save_CXXFLAGS -Werror -Wno-potentially-evaluated-expression"
AC_TRY_COMPILE([],[],[ WNO_POTENTIALLY_EVALUATED_EXPRESSION="-Wno-potentially-evaluated-expression" ],[])
AC_LANG_POP()
CXXFLAGS="$ac_save_CXXFLAGS"
build system: compile without maybe-uninitialized warnings for gcc See e.g. http://stackoverflow.com/questions/21755206/how-to-get-around-gcc-void-b-4-may-be-used-uninitialized-in-this-funct
2015-05-23 17:28:57 +00:00
else
WNO_MAYBE_UNINITIALIZED="-Wno-maybe-uninitialized"
build system: enable gcc's stack protection Implements #1370.
2015-08-11 13:02:58 +00:00
FSTACK_PROTECTOR="-fstack-protector"
build system: compile without maybe-uninitialized warnings for gcc See e.g. http://stackoverflow.com/questions/21755206/how-to-get-around-gcc-void-b-4-may-be-used-uninitialized-in-this-funct
2015-05-23 17:28:57 +00:00
build system: enable gcc's stack protection Implements #1370.
2015-08-11 13:02:58 +00:00
if check_version 4.9.0 $ac_cv_gcc_version ; then
FSTACK_PROTECTOR="-fstack-protector-strong"
elif check_version 4.8.0 $ac_cv_gcc_version ; then
build system: compile without maybe-uninitialized warnings for gcc See e.g. http://stackoverflow.com/questions/21755206/how-to-get-around-gcc-void-b-4-may-be-used-uninitialized-in-this-funct
2015-05-23 17:28:57 +00:00
WLOGICAL_OP="-Wlogical-op"
fi
build system: move compiler warning flag checks to their own file
2013-10-26 10:03:20 +00:00
fi
build system: enable gcc's stack protection Implements #1370.
2015-08-11 13:02:58 +00:00
AC_SUBST(FSTACK_PROTECTOR)
build system: move compiler warning flag checks to their own file
2013-10-26 10:03:20 +00:00
AC_SUBST(QUNUSED_ARGUMENTS)
AC_SUBST(WNO_SELF_ASSIGN)
AC_SUBST(WNO_MISMATCHED_TAGS)
AC_SUBST(WLOGICAL_OP)
build system: check for and turn off some new warnings from clang++ 3.6 These warnings include -Winconsistent-missing-override and -Wpotentially-evaluated-expression which are both triggered by code out of my control (Qt and wxWidgets).
2015-03-25 16:51:30 +00:00
AC_SUBST(WNO_INCONSISTENT_MISSING_OVERRIDE)
AC_SUBST(WNO_POTENTIALLY_EVALUATED_EXPRESSION)
build system: compile without maybe-uninitialized warnings for gcc See e.g. http://stackoverflow.com/questions/21755206/how-to-get-around-gcc-void-b-4-may-be-used-uninitialized-in-this-funct
2015-05-23 17:28:57 +00:00
AC_SUBST(WNO_MAYBE_UNINITIALIZED)
Reference in New Issue Copy Permalink