In Qt 6.4 (on macos) Debug build does not generate javascript file...

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

I am not sure Qt signals would work. You should certainly be able to so callbacks though.

Problem solved by removing the emrun flag. I can now specify custom arguments in the qtloader.js using emscripten's Module.arguments like this :

Module['arguments'] = ['FirstArg', 'SecondArg'];

pro:

wasm: INCLUDEPATH += "C:\emsdk\upstream\emscripten\cache\sysroot\include"

Settings for Qt 6.6.3:

image.png

@Ahmed-Yarub-Hani-Al-Nuaimi Oh ok I see, thanks for your time !

Short answer... you can't get the full file path of a file.

Your question is more related to safety/security standards regarding major browsers and the decisions related to them made by owner companies/foundations.

That is, javascript is not allowed to know the full path of a file shared by the user. So, fileContentReady or in general any webassembly function will end up being a javascript function, limited to the security standards imposed on js implementation by the browser.

(You can always ask the user to install a java applet :P )

@lorn-potter thanks for your command.
I love working with QT. If WASM would be working, a complete new world would open for us. The main thing what annoys me is that I can not find a good manual/guide to get wasm running on linux. I hope somebody can point me in the good direction. I'm probably just missing the needed information/knowledge, but I really want to learn!