Good idea, I added that in https://github.com/kripken/emscripten/pull/5992 . It will mention the FORCE_FILESYSTEM option, which will export all those methods for you, when the file packager is run standalone. (We already had this in the docs and at runtime in -O0 and ASSERTIONS builds, but even better to print it from the tool itself, where it is most likely to be seen.)
On Tue, Dec 26, 2017 at 1:17 AM, Александр Гурьянов <[email protected]> wrote: > Hi. I have recently switched to new version of emcc, and faced with > the problem that I should add functions to -s > EXTRA_EXPORTED_RUNTIME_METHODS to use them through > Module['function_name'] > > Most of errors that I have came from file_packager.py, I mean I used > file_packager.py to create preloadable FS, and I found that this > functions should be added to EXTRA_EXPORTED_RUNTIME_METHODS: > > ['getMemory', 'addRunDependency', 'removeRunDependency', > 'FS_createPath', 'FS_createPreloadedFile', 'FS_createDataFile'] > > I think that it will be good if file_pacakger will give advice what > functions I need to include into EXTRA_EXPORTED_RUNTIME_METHODS, > because currently I find this function by incremental tries. > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
