diff options
| author | Cedric BAIL <cedric@osg.samsung.com> | 2016-11-15 14:04:54 -0800 |
|---|---|---|
| committer | Cedric BAIL <cedric@osg.samsung.com> | 2016-11-15 14:10:06 -0800 |
| commit | dc7806e6856b584b387b0126f994e461f7c897cf (patch) | |
| tree | fa65305cefeb083ae4a529017fb554a715a05033 | |
| parent | a1e1bb01bafffdf5920f6947b4d99b8c5b9c5621 (diff) | |
| download | efl-dc7806e6856b584b387b0126f994e461f7c897cf.tar.gz | |
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.
| -rw-r--r-- | configure.ac | 8 |
1 files changed, 1 insertions, 7 deletions
diff --git a/configure.ac b/configure.ac index 795eb414db..3c4eb481bd 100644 --- a/configure.ac +++ b/configure.ac @@ -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]) |