From c968c787e5f39734a8cd15b1650f9db78bb36ed4 Mon Sep 17 00:00:00 2001
From: Leon Krause
Date: Sun, 18 Mar 2018 21:33:54 +0100
Subject: Disable Emscripten assertions in release_debug builds

The messages generated by some assertions can be confusing to users.

(cherry picked from commit d6c9d8d778954c65d69d1af04a9921d8887dec9f)
---
 platform/javascript/detect.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'platform/javascript/detect.py')

diff --git a/platform/javascript/detect.py b/platform/javascript/detect.py
index 485a586f2..2bd55af4a 100644
--- a/platform/javascript/detect.py
+++ b/platform/javascript/detect.py
@@ -65,13 +65,14 @@ def configure(env):
 
     elif (env["target"] == "release_debug"):
         env.Append(CCFLAGS=['-O2', '-DDEBUG_ENABLED'])
-        env.Append(LINKFLAGS=['-O2', '-s', 'ASSERTIONS=1'])
+        env.Append(LINKFLAGS=['-O2'])
         # retain function names at the cost of file size, for backtraces and profiling
         env.Append(LINKFLAGS=['--profiling-funcs'])
 
     elif (env["target"] == "debug"):
         env.Append(CCFLAGS=['-O1', '-D_DEBUG', '-g', '-DDEBUG_ENABLED'])
         env.Append(LINKFLAGS=['-O1', '-g'])
+        env.Append(LINKFLAGS=['-s', 'ASSERTIONS=1'])
 
     ## Compiler configuration
 
-- 
cgit v1.2.3-70-g09d2