Starting with 2.1.21, in order to make the default output size smaller some
runtime functions are transitioning to library functions.  In debug builds,
if you try to use these functions, you should see an actionable warning.

>From the changelog:

- The `LEGACY_RUNTIME` setting is no longer enabled by default.  If you use
any
  of these legacy runtime functions (except in library code with explicit

  dependencies) then you would need to set `LEGACY_RUNTIME` on the command
line
  or add the ones you need to `DEFAULT_LIBRARY_FUNCS_TO_INCLUDE`:

   - addFunction

   - removeFunction

   - allocate

   - AsciiToString

   - stringToAscii

   - UTF16ToString

   - stringToUTF16

   - lengthBytesUTF16

   - UTF32ToString

   - stringToUTF32

   - lengthBytesUTF32

   - allocateUTF8

   - allocateUTF8OnStack

   - writeStringToMemory

   - writeArrayToMemory

   - writeAsciiToMemory

   - intArrayFromString

   - intArrayToString

   - warnOnce

   - ccall

   - cwrap

  Although this is technically a breaking change for those who use these

  functions, there are assertions in debug builds that catch such usages
and
  direct towards how to fix the issue.

I hope this change is not too disruptive and overall a move in the right
direction.

cheers,
sam

-- 
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/CAL_va2_a5BQUuuR6mhS%2BGT056UtefVRs--SKbss2Pau%3D%2BOtXhg%40mail.gmail.com.

Reply via email to