-
Notifications
You must be signed in to change notification settings - Fork 176
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
natives/*.js missing in build/release #483
Comments
I added another way to register native modules with DoppioJVM, and opted to use that method for the built-in natives to remove some startup cost. You have two options:
|
Sorry, but I do not understand - even both options :-( For both options I need the *.js files - but they are not be built anymore?!?
I am missing the folder "natives" with the (native) js-files? |
@cool2man I updated the documentation; hope it clarifies. https://github.com/plasma-umass/doppio/tree/master/docs#adding-native-methods-using-doppioh |
Sorry. I didn't got it. Let us complete reset the question: I try to use doppio in my own website using this document: https://github.com/plasma-umass/doppio/tree/master/docs Step 0: works! Step 1: As I don't have the generated natives/*.js any longer in in build/release, I created my web folder without them. Step 2: On start of the virtual machine the builtin natives are missing; this results into the error: Error constructing JVM: Failed to resolve java/lang/Thread. |
@cool2man In Step 1, make sure you're configuring this setting properly: // The first argument is the filename of the listings file
// The second argument is the relative URL to the folder containing the listings file
// and the data it indexes.
// In this example, the listings file and DoppioJVM's data is at
// <thiswebpage>/doppio/listings.json
mfs.mount('/sys', new BrowserFS.FileSystem.XmlHttpRequest('listings.json', 'doppio')); It's very possible that you are not passing the correct path to |
After building the project
I could not find the natives directory inside build/release.
This situation has changed since my last build on an older version (at the begin of September).
Without these js-files, I can't get my solution running inside browser.
The text was updated successfully, but these errors were encountered: