ionic-cordova-gulp-seed icon indicating copy to clipboard operation
ionic-cordova-gulp-seed copied to clipboard

ifconfig and awk are unknown command on Win 7,..

Open Claus1 opened this issue 11 years ago • 10 comments

gulp command doesn't work for me on Win 7. I think it's a problem for all Win users.

Subj message is the first. The second is c:\MyProjects_ionic\node_modules\execSync\index.js:69 throw new Error('ERROR: output not captured'); ^ Error: ERROR: output not captured at Object.exec (c:\MyProjects_ionic\node_modules\execSync\index.js:69:11) at Object. (c:\MyProjects_ionic\gulpfile.coffee:28:56) at Object. (c:\MyProjects_ionic\gulpfile.coffee:1:1) at Module._compile (module.js:456:26)

Claus1 avatar Jul 30 '14 15:07 Claus1

Yeah, you're right.

You can fix it in 2 ways (see https://github.com/jtomaszewski/ionic-cordova-gulp-seed/blob/master/gulpfile.coffee#L28):

  1. define ENV variable LOCAL_IP (f.e. `LOCAL_IP="127.0.0.1" gulp)
  2. modify gulpfile.coffee and define LOCAL_IP manually

jtomaszewski avatar Jul 30 '14 16:07 jtomaszewski

It helped partially. Now I see c:\MyProjects_ionic>gulp [23:04:33] Warning: gulp version mismatch: [23:04:33] Global gulp is 3.8.6 [23:04:33] Local gulp is 3.6.2 gulp.env has been deprecated. Use your own CLI parser instead. We recommend usin g yargs or minimist. [23:04:35] Using gulpfile c:\MyProjects_ionic\gulpfile.js [23:04:35] Starting 'default'... [23:04:35] Starting 'build'... [23:04:35] Starting 'clean'... [23:04:35] Starting 'bower:install'... [23:04:35] Finished 'clean' after 17 ms [23:04:36] Finished 'bower:install' after 1.34 s [23:04:36] Starting 'assets:ejs'... [23:04:36] Starting 'assets:others'... [23:04:36] Starting 'styles'... [23:04:36] Starting 'scripts:vendor'... [23:04:36] Starting 'scripts:app'... [23:04:36] Starting 'scripts:bootstrap'... [23:04:36] Starting 'templates'... [23:04:37] Finished 'assets:ejs' after 587 ms [23:04:37] Finished 'scripts:bootstrap' after 576 ms [23:04:37] Finished 'scripts:vendor' after 597 ms [23:04:37] Finished 'scripts:app' after 620 ms [23:04:37] Starting 'scripts'... [23:04:37] Finished 'scripts' after 14 ?s [23:04:37] Finished 'templates' after 622 ms [23:04:37] Finished 'styles' after 749 ms [23:04:37] Finished 'assets:others' after 1.13 s [23:04:37] Starting 'assets'... [23:04:37] Finished 'assets' after 12 ?s [23:04:37] Finished 'build' after 2.49 s [23:04:37] Starting 'watch'... [23:04:37] Finished 'watch' after 185 ms [23:04:37] Starting 'server'... [23:04:37] HTTP server listening on 4400 [23:04:37] Finished 'server' after 3.29 ms [23:04:37] Starting 'weinre'... [23:04:37] Finished 'weinre' after 686 ?s [23:04:37] Finished 'default' after 2.68 s [23:04:37] Live reload server listening on: 35729

events.js:72 throw er; // Unhandled 'error' event ^ Error: spawn ENOENT at errnoException (child_process.js:980:11) at Process.ChildProcess._handle.onexit (child_process.js:771:34)

c:\MyProjects_ionic>

Claus1 avatar Jul 30 '14 16:07 Claus1

Seems like most of the tasks are working. Try running them 1by1 to see which triggers the error. Maybe gulp watch ? (livereload server).

jtomaszewski avatar Jul 30 '14 16:07 jtomaszewski

the problem in "weinre"

Claus1 avatar Jul 30 '14 16:07 Claus1

OK, then remove the weinre completely from the gulp 'default' task - it's a remote debugger that isn't really needed.

jtomaszewski avatar Jul 30 '14 16:07 jtomaszewski

ok but why gulp default and build-debug command doesnt start web page in browser? I have to realize howto and do it manually?

Claus1 avatar Jul 30 '14 16:07 Claus1

It runs the web server, but also stuff like live reload server and weinre debugger server.

jtomaszewski avatar Jul 30 '14 19:07 jtomaszewski

but I don't see the running application in browser. Any other build systems I used do this that's why it looks like a error for me. My question is there a command in gulpfile for the running application in browser or due to a bug or win 7 incompatibility?

Claus1 avatar Jul 30 '14 19:07 Claus1

gulp server (which is included in the default gulp command) runs the server by default on the 4400 port - so you can visit localhost:4400 in your browser.

You can run gulp --open and it will try to open the browser automatically, but this thing actually won't work on Windows, sorry. (the server should work, though)

I don't use Windows anymore, so I can't help you much with it, sorry.

jtomaszewski avatar Jul 30 '14 19:07 jtomaszewski

Thanks! )

Claus1 avatar Jul 30 '14 19:07 Claus1