Thanks Floh. Most of the source code is our own besides the mentioned emscripten ports.
I am not sure for what emscripten uses libc, but I guess it is not compiled to asm.js / WASM since its actual implementation cannot be simply realized in the browser. Or maybe I am missunderstanding and this is exactly what they do. Floh schrieb am Dienstag, 26. April 2022 um 19:19:11 UTC+2: > I'm neither part of the Emscripten team or a lawyer, so take my answers > with a huge grain of salt. > >> >> 1. Under which license and copyright is the from emscripten generated >> code? >> >> Emscripten doesn't matter in this case, only the license of the source > code that's compiled. > >> >> 1. As far as I know, there are JavaScript / Browser implementations >> of libc in order to be able to execute code which uses these APIs. Under >> which license and copyright is this code? Is there a specific source code >> folder which holds this implementation so that I can focus my intention >> on >> this particular folder? >> >> AFAIK Emscripten uses MUSL as libc (https://musl.libc.org/) which is > liberally licensed (MIT License: > https://git.musl-libc.org/cgit/musl/tree/COPYRIGHT). > > Standard MIT license may require attribution, at least that's what I've > been told is the main difference to the even more liberal zlib/libpng > license. > >> >> 1. Is there a difference regarding emitting asm.js and WASM in the >> context of license and copyright? (there is obviously a technical >> difference, but I am not interested in this at the moment) >> >> I don't think so. > >> >> 1. Is in the generated code anything which was copied or otherwise >> added which orignally stems from another open source software? What comes >> to my mind are things like polyfills which could be generated into the >> code >> in order "to make things work" etc.. (I am aware of emscripten ports and >> we >> specifically use FreeType, Harfbuzz and ICU. But is there more than that). >> >> This is actually something the Emscripten team needs to answer. The > toolchain license itself should not "bleed into" the compiler output, but > there may be some sources compiled into the resulting program where the > license matters (such as MUSL). > > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/22f17594-40b8-4dc5-b22f-9f622180e368n%40googlegroups.com.
