Skip to content
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

nw_elf.cll missing in generated .exe #186

Closed
QuinDennis opened this issue Mar 6, 2017 · 10 comments
Closed

nw_elf.cll missing in generated .exe #186

QuinDennis opened this issue Mar 6, 2017 · 10 comments

Comments

@QuinDennis
Copy link

created Win32 app on Ubuntu16 version, it generated an 'output' folder with an .exe (and nwjs files). Copied the exe to Win32 and ran,
-System Error
The program can't start because nw_elf.dll is missing...

Next, copied the whole output folder from U16 to Win32, ran the exe, seemed to execute but never produced an NWJS app screen

@jyapayne
Copy link
Collaborator

jyapayne commented Mar 6, 2017

Yes, you need to copy all the files in the output folder in order for the exe to run.

As for the NWJS app screen, there might be some issues with your app starting. What's in your package.json?

@QuinDennis
Copy link
Author

QuinDennis commented Mar 6, 2017

OK, copying whole folder was my second try above. But, I was under the impression it would make a single EXE, guess not. In fact, that's exactly what the 'What Is It?' section states.

JSON
{
"name": "awfiles",
"version": "0.1",
"main": "index.html",
"window": {
"toolbar": true
}
}

@jyapayne
Copy link
Collaborator

jyapayne commented Mar 6, 2017

I've updated the readme to better reflect what actually happens. Unfortunately, bundling as a standalone exe (with libraries inside the exe) is not feasible for me to do.

That's interesting. Is there anything special in your index.html?

@QuinDennis
Copy link
Author

Very plain, (and BTW, thanks for your work.

Here is a command in Windows which makes a single working EXE. copy /b nw.exe+app.nw app.exe

<title>APP</title> <script type="text/javascript" src="index.js"></script>

@jyapayne
Copy link
Collaborator

jyapayne commented Mar 6, 2017

You're welcome. If only it worked out of the box most of the time ;)

Maybe check the error log and see if there's anything that jumps out. It's located in ~/.local/share/Web2Executable/files/error.log on Ubuntu.

Web2Exe basically does the command you just wrote, but in a (supposedly) more friendly way. Sometimes there are errors that cause the build process to silently fail or partially succeed. If I had time these days, I would much improve the build system to show these errors.

@QuinDennis
Copy link
Author

no error.log

@jyapayne
Copy link
Collaborator

Looks like no error log might be related to #187

@jyapayne
Copy link
Collaborator

jyapayne commented Mar 19, 2017

I've figured out what might be the issue. As a workaround, edit the whitelist section (simply put a space, and then backspace) and this should update the filters to include the package.json. I will fix this asap!

This happens if your project doesn't originally have a package.json and that file is generated by Web2Exe.

jyapayne added a commit that referenced this issue Mar 19, 2017
Logging is now enabled and filters refresh on no package.json
@jyapayne
Copy link
Collaborator

@QuinDennis I've fixed the exporting of a simple project. It was just the package.json not being copied if it didn't exist already.

@QuinDennis
Copy link
Author

QuinDennis commented Mar 19, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants