-AC_ARG_WITH([over-tizen_2_2],
- [AC_HELP_STRING([--with-over-tizen_2_2],
- [Use tizen API over ver. 2.2])],
- [with_over_tizen_2_2=yes],
- [with_over_tizen_2_2=no])
+# node.js by default statically links against libuv, so it doesn't need to install
+# a libuv headers/ shared library. So we can't use pkg-config to access any headers.
+# As a work around we pass the node deps path so we can access the libuv headers inside nodes
+# directory
+AC_ARG_WITH([libuv],
+ [AC_HELP_STRING([--with-libuv],
+ [Path that contains libuv headers. Setting this configures DALi to work with LibUV mainloop used in Node.JS.
+ For example /usr/tmp/downloads/node/deps/uv/include/ ])],
+ [with_libuv=$withval],
+ [with_libuv=no])
+
+# Node.JS already has a libuv main loop running,so we have to integrate with it
+AM_CONDITIONAL(LIB_UV_EVENT_LOOP, test x$with_libuv != xno)
+
+
+build_for_libuv=no
+if test "x$with_libuv" != "xno"; then
+ AC_MSG_NOTICE("build with libuv mainloop (Node.JS support) == yes");
+ [build_for_libuv=yes]
+ DALI_ADAPTOR_CFLAGS="$DALI_ADAPTOR_CFLAGS -DNODE_JS_SUPPORT -I${with_libuv}"
+else
+ #not using libuv build
+ AC_MSG_NOTICE("build with libuv mainloop == no (Node.JS not supported)");
+fi
+
+AC_ARG_ENABLE([appfw],
+ [AC_HELP_STRING([--enable-appfw],
+ [Builds with Tizen App framework libraries, off by default])],
+ [enable_appfw=$enableval],
+ [enable_appfw=no])
+
+# Option to allow building with Tizen SDK 2.2
+AC_ARG_WITH([tizen-2-2-compatibility],
+ [AC_HELP_STRING([--with-tizen-2-2-compatibility],
+ [Use Tizen SDK 2.2 compatibility])],
+ [with_tizen_2_2_compatibility=$withval],
+ [with_tizen_2_2_compatibility=no])