Qt for WebAssembly

I am using 5.15.2

@just_a_developer said in Webassembly - Typescript support: Would it be possible to have Typescript output with *.ts extension? May I ask why you want this? A *.js file can be integrated into TypeScript code A *.ts files cannot be used directly with HTML websites; they need to be compiled into *.js files first

If you need to access/ show your app via a web browser then WebEngine won't help you at all. You can use WebAssembly or any different web framework (Cutelyst, Django, RoR etc.)

I had the same problem and the problem was the Qt host build haven't qtshadertools module. I recompiled qtshadertools module in Qt host build and solved it

Problem solved. I don't know why, but qt needs to be configured to work with emsdk. Tools->Options->Devices->WebAssembly ...and add root directory.

Short explanation is that the webassembly qpa plugin has no support for the input context. :)

https://bugreports.qt.io/browse/QTBUG-84392 With Qt 6.2, you can use qt-cmake to build examples, which does not have this issue.

This is already fixed in 6.2.3, and 6.3

windows.h is not part of the emscripten sdk, as it does not have the Javascript port of the windows API. You could port those parts to Qt or SDL.

Without having the faintest of clues about the actual problem, at a glance it looks to me like some missing/incomplete/bogus library support issue. I suggest you bring this to the mailing list, we don't get much traffic for wasm here.

@lorn-potter Yes I want to do something like put a texture on the cube surface in WebAssembly. Could I ask what Qt components should I use? Currently I tried QQuickFramebufferObject and QQuickItem (following the "Scene Graph - OpenGL Under QML" example), but haven't get a successful texture rendering in Chrome browser on Ubuntu 20.04 (Qt version 5.15.2). I also tried without WebAssembly using QOpenGLWidget, in this way the texture works normal.

Thanks Lorn, I will give that a try. Gary

Need more information, such as Qt version, any messages you may see in the browser console.

Try changing add_executable to qt_add_executable

@GirishSharma Any update Please?