-
Notifications
You must be signed in to change notification settings - Fork 285
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
node-java v0.12.2 fails with electron-rebuild (fatal error LNK1120) #541
Comments
How did you solve this problem? |
I didn't find a solution for this problem as of now, I'm still hoping for an answer. |
Hi, my email: [email protected] |
@jianchang69 You should use npm to get the dependencies. Just pin the version to |
thank DManstrator, |
Yeah, that's exactly the same issue I currently face hence why I opened this issue. I still need to find a new approach to this since this library seems unmaintained. In worst case, I have to re-implement everything in a different language. But for now, it's pretty low on my ToDo list. |
The same problem |
The same... |
For me solved here: lygstate/node-java #532 |
hi, ddrigass I doubte here is problem: |
Thanks, it works at electron 24.1.2 |
Hello.
When using version
0.12.1
, building and running the electron app works, but not with using version0.12.2
.When I try to use the code below, it fails on
0.12.2
sinceelectronbrowser\src\main\electron\node_modules\java\build\Release\nodejavabridge_bindings.node
does not exist. However on0.12.1
this does exist (see screenshots below). This reflects also what the logs show.Execution:
I would be very glad to get some help on this, spend a day trying to resolve it but without any success. When you need more information, please notify me.
Versions:
Software
Desktop development with C++
Dependencies
Logs / Stacktrace (partially in German)
Folder comparison
Edit 1
Changed setup to make it at least completely runnable on version 0.12.1. This made the issue also less confusing. By now I'm pretty sure that is a bug with node-java.
The text was updated successfully, but these errors were encountered: