-
Notifications
You must be signed in to change notification settings - Fork 302
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
Building on Windows for Windows creates a dummy executable #5
Comments
need to setup a windows vm to test this - are the tests running on windows? |
Oh I forgot to mention that! No, they're not.
|
These mostly look like path issues - building on windows should work now can you give it a try? Tested it on a win7 vm |
Talking about creating an app not running the test - if the test work on mac an linux that should be enough :) |
Since it looks like 0.0.1 is still the latest on npm, I just re-ran the tests;
|
|
You can either do:
to test it locally |
Oh yeah of course. It seems the same before though :/. It's not a problem with paths for sure since if I open the contents of the mac one, deep down inside of app.nw I see files I recognize. |
It would be great to get the tests working on Windows btw... I'll try help make that happen |
be my guest :) I only tried the cli version on windows with the exmaple folder - worked fine on a win7 vitrualbox |
@adam-lynch any success getting the tests pass in windows? The build is working for me on windows and I want to update the grunt version on monday. If the app is running on for you on windows pls close the PR and open another one for the tests :) |
@steffenmllr no update on the tests. I'll create a separate PR when I get around to it. The same thing is happening as far as I can see. I am installing the latest from GitHub. Also, sometimes when re-running it, I get this error:
And if I try to build for |
I've tried building on Mac OSX 10.9.1 for Windows, Mac and Linux.
|
Apologies, those tests on the Mac were with
|
which windows operating system are you using? master build works for me on win7 |
Today, the tests were done by a colleague on Windows 7. Before now it was Windows 8. |
Ok I can confirm building for Mac and building for Windows, on Windows, works. (With latest from GitHub). I had this crazy problem(s) where it seemed like having custom/private modules' (which were stored outside of Anyway, it seems to work now fine except building for |
It just creates a
nw.exe
which shows "node-webkit" in ASCII art.My usage:
It is at least taking some information from
dist/package.json
because indist
there's a directory with thename
field as its name (and then a directory per platform inside, of course).The text was updated successfully, but these errors were encountered: