Sharing some stuff <https://github.com/arielm/chronotext-cross> I'm currently developing, definitely on topic (as-long-as CMake is an option...)
1) Dealing with packaged-files via NODEFS <https://github.com/arielm/chronotext-cross/tree/803d7a2/tests/TestingFileSystem1> - Cons: only works with node - Pros: lightweight executable, *true* file-system Additional entry points: - em_link_pre_js <https://github.com/arielm/chronotext-cross/blob/803d7a2/core/cmake/test.simple.cmake#L27> - pre.js <https://github.com/arielm/chronotext-cross/blob/803d7a2/core/cmake/emscripten/pre.js> 2) Dealing with packaged-files via embed-file <https://github.com/arielm/chronotext-cross/tree/803d7a2/tests/TestingFileSystem2> - Cons: heavy executable (data is not simply encoded as raw-binary...) - Pros: works with node, mmap friendly Additional entry points: - embed-file <https://github.com/arielm/chronotext-cross/blob/803d7a2/core/cmake/test.complex.cmake#L69> HTH, Ariel On Wednesday, July 15, 2015 at 11:55:33 PM UTC+3, Klaus wrote: > > I've successfully been using the file_packager.py to package data files > for my ports in the browser, but i just noticed the following: > > using preloaded data can only be done on a web page or in a web worker'; > > > When running ports from node, how are they able to load data? Directly > from the filesystem, relative to where the script is, like a normal > executable? If not, is there a way to package data for them? > -- 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.
