Look into licensing for webassembly target

[desperadoduck]

If the code is built as webassembly application, essentially a big .wasm file is created which contains the application as well as needed library code. This wasm file is then executed in the user's browser. That means that essentially the library code is in some way distributed to the user's browser. That is in itself no problem as Qt is (L)GPLv3 and may be distributed with a GPLv3 application. But Qt also contains 3rd-party code, which might require additional license notices when being distributed.
We should make sure that nobody accidentally violates any license requirement by deploying the .wasm on their server. The most secure way would probably be, to recommend to build a stripped down Qt. library, where all but the essential 3rd-party libraries are disabled. Then look into the remaining 3rd party libraries and their licenses and add the necessary attributions to the license dialog. What would be nice, would be some automatic checking, if the used Qt build uses additional 3rd party licenses, and let the build fail in that case.
Sigh, I just wanted to have some fun coding, but it looks complicated. Any pointers/ideas?

[desperadoduck]

added a notice to the readme, that you should not blindly put the binary webassembly application on your server.