Hi @mosra !

As these feature are getting ready/are ready in modern browsers, here's a proposal how they could be supported in the toolchain.

Best, Jonathan

The default EMSCRIPTEN detection is based on a global EMSCRIPTEN variable. If we use these toolchains, this variable won't be set making crosscompilation fail

Hi @mosra !

This is a tiny one: Newer emscripten versions produce a loud warning when using linker-only flags during compilation:

em++: warning: linker setting ignored during compilation: 'WASM' [-Wunused-command-line-argument]

I went ahead and removed it from CMAKE_CXX_FLAGS_INIT.

Best, Jonathan

Hi, I'm trying to build sdl2 from sources here: https://github.com/SDL-mirror/SDL The cmake config goes fine with the ios toolchain, but builds fail complaining about missing headers, etc.

I use the following steps:

mkdir build-ios && cd build-ios
cmake .. \
    -DCMAKE_TOOLCHAIN_FILE=../toolchains/generic/iOS.cmake \
    -DCMAKE_OSX_SYSROOT=/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk \
    -DCMAKE_OSX_ARCHITECTURES="arm64;armv7;armv7s" \
    -DCMAKE_INSTALL_PREFIX=~/ios-libs \
    -G Xcode
cmake --build .

Hi @mosra !

Since setting up emscripten on a new computer, I finally found time to properly fix this issue: when using github.com/juj/emsdk the toolchain will autodetect the Emscripten Prefix from the environment, but it is set as a Windows path and produces syntax errors in the generated ninja build files.

My previous workaround was to manually specify a normalized path to emscripten, but cleaning the path in the toolchain is way cleaner imo.

This allows for super straight forward, frictionless use of the Toolchain (except that on Windows, MSVC generator will be chosen automatically, so you do still have to specify -GNinja.)

Cheers, Jonathan

https://github.com/mosra/toolchains/blob/d7beaeddc68c5ee07603f1c87cef4d4323c6f0f4/generic/Emscripten-wasm.cmake#L17

Hi, there is a typo if(DEFIEND ENV{EMSCRIPTEN}) should be if(DEFINED ENV{EMSCRIPTEN}) Best, Tomas

Creating an issue here s.t. this can be addressed when https://developercommunity.visualstudio.com/t/Debug-android-device-through-cmake-proje/10087552 this is given a reply to.

When enable IPO for CMake, it defaults to ThinLTO on Clang which is much faster than normal LTO, but does occasionally run into issues. #14 brings us part of the way there and immediately solves the issue with Full LTO. One of the main blockers is a bug in the EMSDK Toolchain here: https://github.com/emscripten-core/emscripten/issues/12763 but there is also a workaround in the first issue about the naming of the archive libraries and object files. We should look into solving that in this toolchain as well.

This properly sets the EMAR for InterproceduralOptimization as described here: https://github.com/emscripten-core/emscripten/issues/11143 and here https://github.com/mosra/magnum/issues/490

The Emscripten upstream backend uses the standard -flto option and emits a warning when --llvm-lto is used.

emcc:WARNING: --llvm-lto ignored when using llvm backend

One way to check whether the fastcomp backend is being used is to check for Clang 6.0.1 or older. Fastcomp stopped being supported with Emscripten > 1.40.1 which has that version. Upstream as old as 1.38.33 (oldest version I could get from emsdk) uses Clang 9.

However, the following doesn't work because the toolchain file doesn't have access the compiler version (CMAKE_CXX_COMPILER_VERSION is only detected by CMake afterwards):

if(CMAKE_CXX_COMPILER_VERSION VERSION_LESS 7.0)
    set(CMAKE_EXE_LINKER_FLAGS_RELEASE_INIT "-O3 --llvm-lto 1")
else()
    set(CMAKE_EXE_LINKER_FLAGS_RELEASE_INIT "-O3 -flto")
endif()

I fixed it with a

string(REPLACE "--llvm-lto 1" "-flto" CMAKE_EXE_LINKER_FLAGS_RELEASE ${CMAKE_EXE_LINKER_FLAGS_RELEASE})

in my code but the correct flag in the toolchain depending on the backend would be nicer.

I've just managed to get up to apk packaging completing, and now trying to debug, I've initially tried importing the APK through Android Studio (option: Profile or debug APK), but I'm getting errors when selecting the cmake built file:

APK Import
Unable to find file
'Users/hkim809/ApkProjects/MyApplication/small/classes.dex'

Any ideas?