efl: disable backtrace for release too

Desktop / Enlightenment / EFL Core Libraries - Cedric BAIL [osg.samsung.com] - 15 November 2016 16:10 UTC

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.


diff --git a/configure.ac b/configure.ac
index 795eb41..3c4eb48 100644
--- a/configure.ac
+++ b/configure.ac
@@ -85,13 +85,7 @@ case "${build_profile}" in

-case "${build_profile}" in
- dev|debug)
- prefer_assert="yes"
- 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])

dc7806e efl: disable backtrace for release too.
configure.ac | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)

Upstream: git.enlightenment.org

  • Share