Installation on Windows

[ryanflorence]

Installation on Windows

[ryanflorence]

Looking at the output it is a sync-prompt issue, would you mind opening this ticket there? https://github.com/shovon/sync-prompt

[dani-z]

Thanks @rpflorence. I opened a ticket there with the same scenario.

Best,

[ryanflorence]

can you link to that ticket? I'll keep this open until its fixed there, or we decide to use something else since ember-tools is still broken until then.

[dani-z]

Yep sure.
Ticket is shovon/sync-prompt#2

And would be great to have something working on windows too.

Thanks,

[dani-z]

Seems that the issue bounce from one dependence to another.
@rpflorence is there a way to not use these?

Thanks,

[shovon]

If ember-tools is considered broken, then so are Geddy, socket.io, bcrypt, and all others that rely on C++ to work. As one goes deeper and deeper into Node.js and its community, one will surely come across a module written in native code. And for all those Windows developers, we suddenly have more and more projects that are considered "broken" as a result.

Frankly, I find this to be purely an issue with node-gyp and/or Windows. Not with ember-tools, nor sync-prompt.

[dani-z]

Yes, I never stated that the issue was related to ember-tools nor
sync-prompt.
I said that for now I did not had any success installing node-gyp on
Windows 8.

Sorry if I created some kind of confusion.

Cheers

On Sun, Jul 21, 2013 at 12:58 AM, Salehen Shovon Rahman <
[email protected]> wrote:

If ember-tools is considered broken, then so are Geddyhttp://geddyjs.org/,
socket.io, bcrypt, and all others that rely on C++ to work. As one goes
deeper and deeper into Node.js and its community, one will surely come
across a module written in native code. And for all those Windows
developers, we suddenly have more and more projects that are considered
"broken" as a result.

Frankly, I find this to be purely an issue with node-gyp and/or Windows.
Not with ember-tools, nor sync-prompt.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/71#issuecomment-21301163
.

*Daniel Zaremba
*
Founder • Blue-FX Design & Development Studio
Javascript Engineer • Freshbyte

http://goog_408397625
[phone]
[email protected] | www.blue-fx.org | www.freshbyte.ro
http://www.technologywithpassion.com/

[shovon]

Yes, I never stated that the issue was related to ember-tools nor sync-prompt.

You didn't, but @rpflorence did.

I'll keep this open until its fixed there, or we decide to use something else since ember-tools is still broken until then.

[Steve-OH]

I had the same problem with my latest attempt to refresh ember-tools to get back in sync. As noted above, the problem occurs during node-gyp compilation of whatever C/C++ code is included in a package. I was not able to figure out exactly why its was failing (the proximal error was "C1902: Program database manager mismatch; please check your installation"), but I was able to reproduce it in Visual Studio using the .vcxproj file generated by node-gyp. I assume that there is a problem somewhere in the configuration options.

Anyway, despite a LOT of attempts (I lost about two days to this...) I never did manage to make Visual Studio Express 2012 happy again (even though it was working just fine before). What I did succeed in doing, however, was get node-gyp to work with Visual Studio Express 2010. Steps:

1. Uninstall Visual Studio 2012 Express, including any updates.
2. Uninstall Windows SDK 7.1.
3. Uninstall Visual C++ 2010 SP1 Compiler Update for the Windows SDK 7.1.
4. Uninstall Visual Studio 2010 SP1.
5. Uninstall Visual Studio 2010 Express.
6. Uninstall any Visual Studio 2010 redistributables.
7. Examine the registry and delete any keys relating to the two deleted Visual Studio versions:

HKCU\Software\Microsoft\VisualStudio\10.0
HKCU\Software\Microsoft\VisualStudio\11.0
HKLM\SOFTWARE\Microsoft\VisualStudio\10.0
HKLM\SOFTWARE\Microsoft\VisualStudio\11.0

8. Install Visual Studio 2010 Express.
9. Install Windows SDK 7.1.
10. Install Visual Studio 2010 SP1.
11. Install Visual C++ 2010 SP1 Compiler Update for the Windows SDK 7.1.
12. Cross your fingers.

[shovon]

@Steve-OH was this an issue with Windows 7 or Windows 8?

[shovon]

@Steve-OH and also, thanks a lot. And sorry to hear that it took up two days of your time. :(

[Steve-OH]

This was Windows 7 x64.

I blame Microsoft for the lost time. ;-) There are simply too many incompatible combinations of configuration options with Visual Studio, and the resulting error messages are completely useless in diagnosing the problem.

[brian-gates]

I'm also having issues with installing this on Windows 7. It worked fine on another machine.

C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\Microsoft.Cpp.x64.Targets(514,5): error MSB8008: Specified platform toolset (v110) is not installed or invalid. Please make sure that a supported PlatformToolset value is selected. [C:\Users\Brian\AppData\Roaming\npm\node_modules\ember-tools\node_modules\sync-prompt\build\sync_prompt.vcxproj]

More complete dump:
http://pastie.org/pastes/8212948/text?key=vv5lrsk9wpsdnulywun6w

Screengrab:
http://snag.gy/7J7Is.jpg

Trying Steve-OH's recommendation above... Here goes more time =/

[brian-gates]

Dear god, @Steve-OH, it worked. The directions at https://github.com/TooTallNate/node-gyp#installation did not. I believe the only difference was 10) Install Visual Studio 2010 SP1.

[Steve-OH]

One more lost soul rescued from the wilderness. ;-)

[brian-gates]

I'm now getting this mysterious error:

>ember build
undefined:1

^
SyntaxError: Unexpected token

It's probably totally my fault and unrelated to this thread, but there's not much to go on as far as debugging and I'm at quite a loss; any help welcome.

[brian-gates]

Anyone have anything to contribute about my issue above? Not sure where to begin debugging.

[Steve-OH]

I vaguely recall seeing something like that, but I can't remember any details. It may have had something to do with bad syntax in a template definition.

Sorry I can't be any more specific. Since it happens during the build process, I would debug by moving files one by one out of the source tree and seeing if there is a point at which the build runs successfully.

[brian-gates]

Thanks for the suggestion. I'll give that a try. Perhaps this is a good candidate for improved error checking and feedback.

[brian-gates]

Found the issue: #82

[brian-gates]

Now I'm getting Error: ENOENT failures.

Here's the complete output: https://gist.github.com/Zaxnyd/9575ae41d28fa4b98c25

Not sure why this is happening.

[brian-gates]

This fixed it: nodejs/node-gyp#277 (comment)