Updated profiles and raylib game with wasm support

Author: perseoGI

examples/cross_build/emscripten/bindings/conanfile.py

@@ -1,5 +1,6 @@
 from conan import ConanFile
 from conan.tools.cmake import CMake, CMakeDeps, CMakeToolchain, cmake_layout
+from conan.errors import ConanInvalidConfiguration
 
 
 class WasmExampleRecipe(ConanFile):
@@ -16,6 +17,10 @@ def requirements(self):
         self.requires("zlib/1.3.1")
         self.requires("fmt/11.1.4")
 
+    def validate(self):
+        if self.settings.os != "Emscripten":
+            raise ConanInvalidConfiguration("This example is only supported on Emscripten.")
+
     def generate(self):
         deps = CMakeDeps(self)
         deps.generate()

examples/cross_build/emscripten/profiles/asmjs

@@ -1,4 +1,4 @@
-include(base)
+include(./emsdk-base)
 
 [settings]
 arch=asm.js

examples/cross_build/emscripten/profiles/base renamed to examples/cross_build/emscripten/profiles/emsdk-base

@@ -1,31 +1,21 @@
 # Note: this profile uses emsdk package from Conan Center Index 
-# To use a local emsdk installation could be done by:
-# a) Define a platform_tool_requires ensuring CC, CXX, etc are defined correctly in PATH
-#  [platform_tool_requires]
-#  emsdk/<version>
-# b) Define compiler_executables
-#  tools.build:compiler_executables={'c':'emcc', 'cpp':'em++'}
-# c) Define buildenv
-#  [buildenv]
-#  CC=<path/to/emcc>
-#  CXX=<path/to/em++>
-#  AR ..
+# To use a local emsdk installation use -pr:h <wasm32/wasm64/asmjs> -pr:h emsdk-native
 
 [settings]
 build_type=Release
 compiler=emcc
 compiler.cppstd=17  
 compiler.libcxx=libc++
-compiler.version=4.0.9
+compiler.version=4.0.10
 os=Emscripten
 
 [tool_requires]
-emsdk/4.0.9
+emsdk/4.0.10
 ninja/[*]
 
 [conf]
-tools.build:exelinkflags=['-sALLOW_MEMORY_GROWTH=1']
-tools.build:sharedlinkflags=['-sALLOW_MEMORY_GROWTH=1']
+tools.build:exelinkflags+=['-sALLOW_MEMORY_GROWTH=1']
+tools.build:sharedlinkflags+=['-sALLOW_MEMORY_GROWTH=1']
 
 # Set Ninja as default generator as it is faster and will sove issues on Windows
 tools.cmake.cmaketoolchain:generator=Ninja
@@ -36,4 +26,3 @@ tools.compilation:verbosity=verbose
 
 # Distinguish between architectures
 tools.cmake.cmake_layout:build_folder_vars=['settings.build_type', 'settings.arch']
-

examples/cross_build/emscripten/profiles/emsdk-native

@@ -0,0 +1,15 @@
+include(./emsdk-base)
+
+[platform_tool_requires]
+emsdk/4.0.10
+
+[conf]
+tools.build:compiler_executables={'c':'emcc', 'cpp':'em++'}
+
+[buildenv]
+CC=emcc
+CXX=em++
+AR=emar
+NM=emnm
+RANLIB=emranlib
+STRIP=emstrip

examples/cross_build/emscripten/profiles/wasm32

@@ -1,8 +1,10 @@
-include(base)
+include(./emsdk-base)
 
 [settings]
 arch=wasm
 
 [conf]
 tools.build:exelinkflags+=['-sMAXIMUM_MEMORY=4GB', '-sINITIAL_MEMORY=64MB']
 tools.build:sharedlinkflags+=['-sMAXIMUM_MEMORY=4GB', '-sINITIAL_MEMORY=64MB']
+
+#tools.build:exelinkflags+=['-sMIN_NODE_VERSION=230000']

examples/cross_build/emscripten/profiles/wasm64

@@ -1,10 +1,13 @@
-include(base)
+include(./emsdk-base)
 
 [settings]
 arch=wasm64
 
 [conf]
 # In this early stage of wasm64, ALLOW_MEMORY_GROWTH is not having effect. Also it may not be the most efficient solution.
 # wasm64 for now needs to declare INITIAL_MEMORY as the maximum memory
-tools.build:exelinkflags+=['-sMAXIMUM_MEMORY=16GB', '-sINITIAL_MEMORY=16GB']
-tools.build:sharedlinkflags+=['-sMAXIMUM_MEMORY=16GB', '-sINITIAL_MEMORY=16GB']
+tools.build:exelinkflags+=['-sMAXIMUM_MEMORY=16GB', '-sINITIAL_MEMORY=16GB', '-sASSERTIONS']
+tools.build:sharedlinkflags+=['-sMAXIMUM_MEMORY=16GB', '-sINITIAL_MEMORY=16GB', '-sASSERTIONS']
+
+#tools.build:exelinkflags+=['-sMIN_NODE_VERSION=221600']
+#tools.build:sharedlinkflags+=['-sMIN_NODE_VERSION=221600']