Qt for WebAssembly

after contact the qt support, they suggest me to replace

win32: LIBS += -L$$PWD/../../TinyLib/build-TinyLib-Qt_5_15_0_WebAssembly-Debug/ -lTinyLib

with

wasm:LIBS += -L$$PWD/../../TinyLib/build-TinyLib-Qt_5_15_0_WebAssembly-Debug/ -lTinyLib

It did not work. I used this line to configure:

./configure -DCMAKE_TOOLCHAIN_FILE='$HOME'/Library/emsdk/upstream/emscripten/cmake/Modules/Platform/Emscripten.cmake -qt-host-path /home/anon/Library/qt6.2/qtbase -xplatform wasm-emscripten -debug -prefix $PWD/qtbase -device-option QT_WASM_SOURCE_MAP=1

When I upload the Qt version into QtCreator, the ABI is always

x86-linux-generic-elf-64bit

Instead of

asmjs-unknown-unknown-emscripten-32bit

Preventing any build.

@SimonR Did you check the Compiler tab to see whether there are any warnings/errors?

No, that's the proper way to do it. The Qt logo and all the HTML, JS files generated in a project are just some example/ boilerplate code. You are free to replace it.

You can use emscripten API to read the JavaScript window.location object.

#include <emscripten/val.h> ... emscripten::val location = emscripten::val::global("location"); auto host = location["hostname"].as<std::string>(); auto port = location["port"].as<std::string>();

@lorn-potter Thanks for the information. Yet <emscripten.h> cannot be found!

@Paul09A

Hello, I have the same issue,

Did you manage to solve this? Any workaround?

Thanks

@amphi Hello,

I know it is quite old, but I have the same issue.
Did you solve it eventually?

Thank you

@lorn-potter When using the installer qt-unified-linux-x64-4.1.0-online.run, and picking to install the WebAssembly component for Qt 5.15.2 I do not see any mention of it falling under GPL instead of LGPL. I make sure to install only LGPL components. Is this an oversight in the installer ? For all other modules (Qt Charts etc...) there is an explicit warning that the module is under GPL and not LGPL.

Building OpenSSL with the no-threads option solve the problem in my case.

I don't really search deeper what is the consequences of that build option but maybe it can help someone ;)

If the resource is in a library make sure to invoke Q_INIT_RESOURCE for your resource file (see documentation for details).

Surely! I upload these files via REST API after receiving them in the sandbox.

@nagyimre You don't know what I've read, so don't assume you do. I know all about the bug you posted. I was probably the first Qt developer to experience it. The Qt WebAssembly wiki even mentions this bug, which we put there so developers would see it. https://wiki.qt.io/Qt_for_WebAssembly

I just assumed you were testing with emrun.

My version is 5.15.2

I have never tried building python with emscripten.
You might look at this:

https://chromium.googlesource.com/external/github.com/kripken/emscripten/+/refs/tags/1.36.0/tests/python/readme.md

hope this helps!