The most reliable documentation for emscripten CLI settings is to look at
settings.js in the source:
https://github.com/emscripten-core/emscripten/blob/main/src/settings.js#L99
The default here is indeed 65536 (64*1024).
-- brooke
On Tue, May 14, 2024 at 6:39 AM Stephan Bergmann
wrote:
> One
On Thu, Apr 25, 2024 at 1:31 PM 'Sam Clegg' via emscripten-discuss <
emscripten-discuss@googlegroups.com> wrote:
> Can you confirm if you are now able to completely remove your usage of
> `mainScriptUrlOrBlob`? I'm hoping the number of cases where this is needed
> is now almost zero.
>
Yes, maiS
ntext, where
the base URL for the main JS, worker JS, and binary were all in the same
subdirectory.
-- brooke
>
> On Thu, Apr 25, 2024 at 10:22 AM Brooke Vibber wrote:
>
>> Figured it out -- my code had been setting Module.mainScriptUrlOrBlob
>> without the relative path s
rouble.)
After setting this correctly to include the relative path, it seems happier
and I have a functioning VP9 codec in pthread build too. :D
Huzzah!
-- brooke
On Thu, Apr 25, 2024 at 9:06 AM Brooke Vibber wrote:
> I had a problem updating my ogv.js codec shims to use 3.1.58 with the new
I had a problem updating my ogv.js codec shims to use 3.1.58 with the new
pthreads output, I'll try tracking down exactly what was going wrong but it
seems like the path to the main .js wasn't getted transmitted correctly
through to the worker loader and it would just 404 out with a bad path.
Once
I don't need internals in global scope, but I _do_ need multiple
instantiation if possible for the demuxers and codecs in ogv.js.
If that's dropped, I'll have to rewrite some C and JavaScript code for my
internal APIs to support multiple active data streams in a long-lived
instance with explicit d
