-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Candid Files #17
Comments
that's an interesting idea! Currently it doesn't build a candid file, but it should be relatively easy since you can get JSC.js working with only one or two APIs. You can check out the demo html for the API signature. |
Looks like these are the culprits here. Any advice on how to suss out what the return types are on these "la" and "va"(etc) functions? Looks like there is a good bit of memory management going on here that is handled in the jsc.js file. That shouldn't be too much of an issue as I think I can script the interaction with the dfinity cannister once I have a valid definition file.: var asm = Module["asm"](asmGlobalArg, asmLibraryArg, buffer); Module["asm"] = asm; var ___emscripten_environ_constructor = Module["___emscripten_environ_constructor"] = function() { |
For testing purpose I think you may safely delete some of the functions like |
I'm interested in trying to get this running inside of a DFINITY wasm canister. I think if I get a wasm file and a candid file I can get to a point to poke it with a stick, but I'm not sure if this project produces the candid file. If I have to custom build it, any idea what the function signatures would be to call line entries dynamically? https://sdk.dfinity.org/docs/developers-guide/work-with-languages.html
The text was updated successfully, but these errors were encountered: