forked from enlightenment/efl
efl: disable backtrace for release too.
User get bitten with this more than they benefit from it. Every use of Eina_Log will trigger backtrace which clutter the output, confuse and scare users when they are not suffering anything serious. It is also very trivial for user to turn it on selectively with EINA_LOG_BACKTRACE when reporting a bug. So let's fallback to a saner approach. The alternate logical solution would be for application to just give up on Eina_Log, which is not really acceptable.
This commit is contained in:
parent
a1e1bb01ba
commit
dc7806e685
|
@ -85,13 +85,7 @@ case "${build_profile}" in
|
|||
esac
|
||||
|
||||
prefer_assert="no"
|
||||
eina_log_backtrace="yes"
|
||||
case "${build_profile}" in
|
||||
dev|debug)
|
||||
prefer_assert="yes"
|
||||
eina_log_backtrace="no"
|
||||
;;
|
||||
esac
|
||||
eina_log_backtrace="no"
|
||||
|
||||
# Enable CRI & ERR backtrace by default for release but not for dev/debug
|
||||
AC_DEFINE_IF([EINA_LOG_BACKTRACE_ENABLE], [test "x${eina_log_backtrace}" = "xyes"], [1], [Default log level triggering backtraces])
|
||||
|
|
Loading…
Reference in New Issue