Windows incompatibility/compile issue

[taylorsmithgg]

W20150409-11:48:47.530(-4)? (STDERR)
W20150409-11:48:47.532(-4)? (STDERR) C:\Users\tsmith\AppData\Local.meteor\packages\meteor-tool\1.1.3\mt-os.windows.x86_32\dev_bundle\server-lib\node_modules\fibers\future.js:245
W20150409-11:48:47.532(-4)? (STDERR) throw(ex);
W20150409-11:48:47.532(-4)? (STDERR) ^
W20150409-11:48:47.532(-4)? (STDERR) Error: %1 is not a valid Win32 application.
W20150409-11:48:47.532(-4)? (STDERR)
W20150409-11:48:47.532(-4)? (STDERR) C:\Users\tsmith\AppData\Local.meteor\packages\npm-node-aes-gcm\0.1.3_6\npm\node_modules\node-aes-gcm\build\Release\node_aes_gcm.node
W20150409-11:48:47.532(-4)? (STDERR) at Module.load (module.js:356:32)
W20150409-11:48:47.532(-4)? (STDERR) at Function.Module._load (module.js:312:12)
W20150409-11:48:47.532(-4)? (STDERR) at Module.require (module.js:364:17)
W20150409-11:48:47.533(-4)? (STDERR) at require (module.js:380:17)
W20150409-11:48:47.533(-4)? (STDERR) at Object.Npm.require (C:\Users\tsmith\WebstormProjects\chaos-box.meteor\local\build\programs\server\boot.js:142:18)
W20150409-11:48:47.533(-4)? (STDERR) at Package (packages/npm-node-aes-gcm/wrapper.js:2:1)
W20150409-11:48:47.533(-4)? (STDERR) at C:\Users\tsmith\WebstormProjects\chaos-box.meteor\local\build\programs\server\packages\npm-node-aes-gcm.js:33:4
W20150409-11:48:47.533(-4)? (STDERR) at C:\Users\tsmith\WebstormProjects\chaos-box.meteor\local\build\programs\server\packages\npm-node-aes-gcm.js:42:3
W20150409-11:48:47.533(-4)? (STDERR) at C:\Users\tsmith\WebstormProjects\chaos-box.meteor\local\build\programs\server\boot.js:222:10
W20150409-11:48:47.533(-4)? (STDERR) at Array.forEach (native)

[aaronjudd]

Looks like a duplicate of #359?

[aaronjudd]

from gitter @taylorsmithgg:

is an issue I've been having lately on a windows platform. Not a major concern, but it would be nice to have the support.
Ran into similar issues with using demeteorizer on Mac, had to manually update the corresponding packages (bcrypt,node-aes-gcm, node-gyp) to the latest versions to get it operational. No such luck on Windows so far.

[taylorsmithgg]

Probably of similar nature if not the exact same. Just figured I'd throw it there for reference.

[kpatyal]

I am getting same error, have you got any solution?

[jenskastensson]

I'm interested in Windows support too, having the same issue.

[kifirkin]

It looks like this issue from meteor meteor/meteor#4087

[kifirkin]

btw also I've noticed that my app wich uses only core package of reaction works without errors.
It was cloned from reaction at early versions

[mpaezmolina]

Hi, is there any updates on this issue? We are really looking forward to run Reaction on Windows. Thanks!

[aaronjudd]

just purchased an actual windows machine, so that we can test and debug windows. stay tuned please.

[aaronjudd]

I’ve made it past all the obvious things (you need to install openssl manually - updated docs with details on this) - so that meteor actually starts correctly now, but there’s still 1 more error that’s crashing meteor with a windows only bug in reaction-core, and frankly I’m stumped because the debug/tracing from meteor doesn’t show any clue as to the root cause event.js:72.

[abhisheksoni27]

Is there any progress to this bug? I cant start developing on reaction because of this. When can we expect this to be resolved?

[aaronjudd]

Still getting an error related to node-aes-gcm, even though openSSL is installed.

)                                            throw(ex);
)                                                  ^
) Error: The operating system cannot run %1.
)
) C:\Users\Aaron\AppData\Local\.meteor\packages\npm-node-aes-gcm\0.

)     at Module.load (module.js:356:32)
)     at Function.Module._load (module.js:312:12)
)     at Module.require (module.js:364:17)
)     at require (module.js:380:17)
)     at Object.Npm.require (C:\Users\Aaron\Documents\Projects\reac
)     at Package (packages/npm-node-aes-gcm/wrapper.js:2:1)
)     at C:\Users\Aaron\Documents\Projects\reaction\.meteor\local\b
)     at C:\Users\Aaron\Documents\Projects\reaction\.meteor\local\b
)     at Array.forEach (native)
)     at C:\Users\Aaron\Documents\Projects\reaction\.meteor\local\b

[abhisheksoni27]

I am getting the eventsjs:72 error on Windows 8.1 . Maybe Windows 10 might be able to look into this?

[aaronjudd]

@abhisheksoni27 can you try:

- download and install Python 2.7.x for Windows 
- download, install Visual Studio Express 2013
- install node.js version 0.10.36 for Windows 
- install the Visual Studio 2008 redistributable required by OpenSSL for Windows.
- download and install the Windows binary OpenSSL distribution. 

in theory you should be able to run: npm install node-eas-gcm at this point, and this might let you past the event.js stage, and past my error. Maybe -- but I'm having problems getting this compiled correctly, but maybe somebody more comfortable with windows can solve this.

@i-a-n I hear you are windows friendly, any chance you can help debug this?

[abhisheksoni27]

@aaronjudd I am going to try that and I will let you know.

[abhisheksoni27]

I tried that and it still did not work. Maybe, we could post this on a windows specific forum so that they might have abetter idea as to what is going on? Or a version specific Node forum?

Also, has this project ever worked on windows? That could help us out too.

[aaronjudd]

imagemagick/graphicksmagic isn't required to run Reaction (though you'll get a message warning that you should install it). I'm not sure Reaction ever compiled on Windows as we only started attempting with Meteor release 1.0. I seem to remember someone saying that they had earlier Reaction versions running, but that could mean any number of dependencies also would have changed. We could try running just core, and removing packages from package.js until we at least have meteor running - that could help identify a particular culprit - but the issues I've worked through so far were all Meteor related.

[abhisheksoni27]

So, what next? Because VirtualBox is fine, but is not the best bet. Also, I removed all packags, and used the basic accounts, and reaction packages, and it still throws the same error.

On Node Specific forums, however, like on SO, it was mentioned that thi error is only thrown when the port node wants is already taken, which completely doesnt make sense in this case, but it might throw some light.

And Maybe, it is about time testing packages, other than core, in projects other than reaction and see if they some damage over there. What do you reckon?

[aaronjudd]

I've spent most of the day trying to debug the event.js error and I'm just not getting anywhere. I'm out of ideas and need to move on. I'd really like to have this fixed - as it's one of the blockers for 0.6.0 release. Happy to offer a bug bounty for resolution (anything will be less painful than trying to debug this!)

[jmonte407]

I was hoping this got resolved also.. We only use windows machines here... This looked like a good project for us to get started with .. anyone know any other projects like reaction? We want to use meteor for our full stack and get rid of .Net.. ASP.Net etc..

[aaronjudd]

@jmonte407 really this "should" be working.. as in I really feel like this is a Meteor problem - you're not cross platform unless you actually work the SAME across platforms. ;-) - there's a couple issues related to this on the Meteor repo, but I'm going to see if we can escalate / see if the wider meteor community can solve.

[jmonte407]

Wow.. Thanks for the response Aaron... I go to many meetups.. we discuss many things related to meteor.. Many of the users have used reaction "Linux users" these users make up about 20% of the users at these meetups.. The rest of us "Windows users - 60 or 70%" in the crowd just sit there saying.. "Has anyone got it to work in Windows"... Reaction looks like a good project... and I agree, should be cross platform....

[kifirkin]

Hi! I'm trying to manually rebuild node-aes-gcm module with node-gyp rebuild, and what I've got, is that error changed to %1 is not a valid win32 application 😭
Also I had to install Win64OpenSSL-1_0_2d.exe

[jmonte407]

Should i uninstall the git i installed earlier? then install msysgit?

[jmonte407]

i've done everything mentioned above.. i am using win 8.1 doesnt work i'm sure its something i'm doin wrong...

[kifirkin]

try to install mingw

[kifirkin]

also try to instal OpenSSL not to win folder: there are second option to install it to c:\OpenSSL-Win**

[jmonte407]

tried both options for openssl... win folder and c:\OpenSSL-Win64.. neither work.... we'll revisit this project when the latest mods have been put in master repo..
Thanks
Jim

[aaronjudd]

@jmonte407 that will be soon, but it's not likely to make any difference in the PiTA windows prereqs. Those are node package requirements, and it's not likely that we're getting rid of oauth.

[jmonte407]

It works!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! was using openssl64.... I downloaded openssl32 did path stuff.. changed git branch to development ... reaction site comes up on port 3000... also a karma site opens up at http://localhost:9876/karma/?id=62022664 ... Thanks you all...

[jmonte407]

So... is coffeescript going away or do I need to learn coffeescript? I don't think I'm savvy enough to contribute to this project ... I want to learn from it... coffeescript threw a wrench in the spokes...

[jmonte407]

oh.. I also had to do this from c:\reaction c:\reaction\meteor add npm-node-aes-gcm

[jmonte407]

aaronjudd && kefirchik && everyone else involved with reaction... Thanks!!!!!!!! "We think meteor along with projects like reaction to learn from with let us depart the .net stack!!"

[aaronjudd]

@jmonte407 congrats! phew. And yes, CoffeeScript will be going away. To be replaced soon with ES6.

[jmonte407]

Nice... :)

[jmonte407]

Does anyone know how to login as admin? docs say it will show up in console.. dont see it...

[kifirkin]

@jmonte407 you can read it here

[jmonte407]

Thanks:)

[aaronjudd]

make sure you pull the latest as well. There was a brief glitch with the logging library.

[jmonte407]

ok

[jmonte407]

how do pull?.. git pull?

[aaronjudd]

@jmonte407 👍
@KEFIRCHIK prettyStream didn't work on OSX. I'm now using bunyan.format can you verify it works for you? If it doesn't, we can add a flag to either switch formatOut stream, or simply document that you can use isDebug='debug' in the settings.json to use 'process.stdOut'

[jmonte407]

ok.. i changes isDebug='debug' in dev.settings.json ... so how do I pull changes in the development branch?

git checkout development
git pull https://github.com/reactioncommerce/reaction
git pull https://github.com/reactioncommerce/reaction-core

??

[jmonte407]

wont my pull overwrite settings.json? if so.. i'll change it again after pulling.. sorry.. new to git also

[jmonte407]

also..my file is dev.settings.json..

[jmonte407]

ok... I ran c:\reaction\meteor after changing to isDebug='debug' got no errors

[jmonte407]

Wow.. I've been playing around with this ... I know its still in Alpha... but you guys are doing an outstanding job... looking forward to next meetup and show other windows users the exact steps to get reaction working on their windows computers..

Thanks again............

[spencern]

@jmonte407 - if you use settings.json instead of dev.settings.json it shouldn't get overwritten after a pull. You may have to copy you content from dev.settings.json to a new file and then save it as settings .json but that should work.

[jmonte407]

yes spencern....I copied dev.settings.json to settings.jon.. then modified settings.json...