#emscripten — Public Fediverse posts

Long shot, but is there anyone here who has used SDL3 and Emscripten or is familiar with building Emscripten from source?

I had to get SDL3_TTF from a PR, and managed to build it with embuilder but so far when I try to build with -sUSE_SDL_TTF=3 it doesn't seem to acknowledge the option and if just complaining that it can't find SDL3/SDL_ttf.h

What am I missing?

(also if you don't know, sharing is caring)

#sdl #sdl3 #emscripten #c #gamedev #programming

Git в браузере. Расширяем возможности с помощью LFS

Привет, Хабр! Я Паша, разработчик

https://habr.com/ru/companies/gram_ax/articles/994384/

#git #libgit2 #lfs #webassembly #rust #ffi #emscripten #docsascode #opensource #localfirst

After again struggeling with #emscripten and the wait4 / wait3 #syscalls, and stumbeling across my 1year+ old bug report on that matter, I just said "Fine, I do it myself" and added the two missing c sources to the build process of emscripten's #libc build xDDDDDD Works flawlessly lmao

#coding #development #programming #c #linux

#Design #Milestones
Photoshop is now on the web · The challenge of bringing a complex desktop app to the browser https://ilo.im/15bbbp

_____
#WebDev #WebPerf #WebAssembly #Emscripten #Browser #WebComponents #ServiceWorkers #WebAPIs

Question on #licenses: Take an #LGPL licensed library written in C, compile it to JavaScript with #emscripten, and bundle it into a JavaScript app. The JavaScript app has to be LGPL licensed because the dynamic linking exception doesn't apply.

Same LGPL library, build a #NodeAPI module that statically links against it, and use that in a JavaScript app. The NodeAPI code would be LGPL'ed since it's statically linked, but would the #JavaScript code be fine since node loads the module dynamically?

Question on #licenses: Take an #LGPL licensed library written in C, compile it to JavaScript with #emscripten, and bundle it into a JavaScript app. The JavaScript app has to be LGPL licensed because the dynamic linking exception doesn't apply.

Same LGPL library, build a #NodeAPI module that statically links against it, and use that in a JavaScript app. The NodeAPI code would be LGPL'ed since it's statically linked, but would the #JavaScript code be fine since node loads the module dynamically?

Question on #licenses: Take an #LGPL licensed library written in C, compile it to JavaScript with #emscripten, and bundle it into a JavaScript app. The JavaScript app has to be LGPL licensed because the dynamic linking exception doesn't apply.

Same LGPL library, build a #NodeAPI module that statically links against it, and use that in a JavaScript app. The NodeAPI code would be LGPL'ed since it's statically linked, but would the #JavaScript code be fine since node loads the module dynamically?

Question on #licenses: Take an #LGPL licensed library written in C, compile it to JavaScript with #emscripten, and bundle it into a JavaScript app. The JavaScript app has to be LGPL licensed because the dynamic linking exception doesn't apply.

Same LGPL library, build a #NodeAPI module that statically links against it, and use that in a JavaScript app. The NodeAPI code would be LGPL'ed since it's statically linked, but would the #JavaScript code be fine since node loads the module dynamically?

Question on #licenses: Take an #LGPL licensed library written in C, compile it to JavaScript with #emscripten, and bundle it into a JavaScript app. The JavaScript app has to be LGPL licensed because the dynamic linking exception doesn't apply.

Same LGPL library, build a #NodeAPI module that statically links against it, and use that in a JavaScript app. The NodeAPI code would be LGPL'ed since it's statically linked, but would the #JavaScript code be fine since node loads the module dynamically?