build: linking C/C++ libraries statically

Toolchains for Win32 used various pthread models and exception handler
models. So we choose to use statically linking C/C++ libraries to avoid
DLL conflict.
(To avoid the problem, we can compile all dependant libararies using same
toolchain, but it needs many efforts and has no many benefits.)

Change-Id: Ie7f116c9872472382d9e2351b239df9e125617a4
Signed-off-by: SeokYeon Hwang <syeon.hwang@samsung.com>

diff --git a/tizen/emulator_configure.sh b/tizen/emulator_configure.sh
index e90c7d36eec3fb0056ef57ba74b62ec25f26b78e..3dbf3582b55cca4f9ecda7fea0dfa52bd809a4d3 100755 (executable)
--- a/tizen/emulator_configure.sh
+++ b/tizen/emulator_configure.sh
@@ -140,6 +140,8 @@ CROSS_MINGW*)
 CONFIGURE_APPEND="
  --cross-prefix=$CROSS_PREFIX
  --enable-werror
+ --extra-cflags=-static-libgcc
+ --extra-cflags=-static-libstdc++
  --extra-ldflags=-Wl,--large-address-aware
  --extra-ldflags=-Wl,--export-all-symbols
  --audio-drv-list=dsound
@@ -154,6 +156,8 @@ CONFIGURE_APPEND="
  --cc=gcc
  --cxx=g++
  --enable-werror
+ --extra-cflags=-static-libgcc
+ --extra-cflags=-static-libstdc++
  --extra-ldflags=-Wl,--large-address-aware
  --extra-ldflags=-Wl,--export-all-symbols
  --audio-drv-list=dsound