Open avital opened 9 years ago
I attempted to publish 0.3.0 onto windows, got this error from the Meteor windows build machine:
richardsmith[rsbatech:robotframework]$ meteor admin get-machine os.windows.x86_32
"install"
npm ERR! node v0.10.36
npm ERR! npm v2.7.3
npm ERR! code ELIFECYCLE
npm ERR! node-expat@2.3.4 install: `node-gyp rebuild`
npm ERR! Exit status 7
npm ERR!
npm ERR! Failed at the node-expat@2.3.4 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the node-expat package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls node-expat
npm ERR! There is likely additional logging output above.
=> Errors while initializing project:
While building package rsbatech:robotframework:
error: couldn't install npm packages from npm-shrinkwrap
C:\Windows\system32>exit
Looks like it's an issue with the Windows build of the stream XML parser library dependencies I used to parse the large RF output.xml file
https://www.npmjs.com/package/node-expat http://node-xmpp.org/doc/expat.html https://github.com/TooTallNate/node-gyp#installation
Hi. Is there any traction in this area? I really would like to user this in my meteor app on windows.
Hi @redji , thanks for your interest in meteor-robotframework. Reading some stack exchange posts like this one seems to indicate there is a general issue building native node modules on Windows .. I have no experience in this area at all. It seems the windows build machines that MDG provide do not have the requisite dependencies at least (see error trace above).
I could replace the streaming xml parser with a js - only xml,parser, but they all read the whole xml file into memory before parsing them afaik. I know that RF output.xml files can be pretty big, and sure to cause such out-of-memory issues.
Hi @rjsmith. Did you try to reach out to them through github? Like it was stated in the first message it was auto generated, so probably nobody read your reply, if you didn't reach out to them.
Hi!
This package has binary dependencies, and we wanted to give you a heads up that Meteor 1.1, with support for Windows will be released in a few days.
Now is the time to publish your package for Windows!
It should be very straightforward -- we've added new build machines that run Windows that you can access with the
meteor admin get-machine
command. This is the same as you've done before for the other architectures we support.For complete directions on how to publish your package for Windows, visit https://github.com/meteor/meteor/wiki/Publishing-a-package-with-binary-dependencies-for-the-Windows-preview
On behalf of the Meteor team, @stubailo, @Slava and @avital.
P.S. This is an automated message based on our database of package authors.