First "official" NodeJS build on Windows • Hacker News Board

Re: First "official" NodeJS build on Windows

#11

Post by xiaoqmangg » Wed, Jul 20, 2011, 11:53 AM UTC

binarymax wrote: post #5

I absolutely love the fact that its just a single exe and not some bloated install. I wish more win software was built like this.

welcometo: http://www.fullmalls.com The website wholesale for many kinds of fashion shoes, like the nike,jordan,prada,, also including the jeans,shirts,bags,hat and the decorations. All the products are free shipping, and the the price is competitive, and also can accept the paypal payment.,after the payment, can ship within short time. free shippingcompetitive priceany size availableaccept the paypal ===== http://www.fullmalls.com =====

jordan shoes $32nike shox $32Christan Audigier bikini $23 Ed Hardy Bikini $23Smful short_t-shirt_woman $15ed hardy short_tank_woman $16Sandal $32christian loubo utin $80 Sunglass $15 COACH_Necklace $27handbag $33AF tank woman $17puma slipper woman $30

===== http://www.fullmalls.com =====

Re: First "official" NodeJS build on Windows

#12

Post by statictype » Wed, Jul 20, 2011, 11:59 AM UTC

This is great. That means both Node.js and Coffeescript should now be natively available on Windows.

Re: First "official" NodeJS build on Windows

#13

Post by wildmXranat » Wed, Jul 20, 2011, 12:34 PM UTC

Just throwing it out there, but what is the real reason behind making it windows friendly? Do developers want it or is it done with intentions to make it more appealing for corporate absorption?

Re: First "official" NodeJS build on Windows

#14

Post by deskamess » Wed, Jul 20, 2011, 12:44 PM UTC

MatthewPhillips wrote: post #10

binarymax wrote: post #5

I absolutely love the fact that its just a single exe and not some bloated install. I wish more win software was built like this.

Why? If you use someone else's library there's going to be a dll associated. Node doesn't have any dependencies.

Does a javascript engine like V8 have to be installed separately to avoid dependency issues?

Microsoft has the Chakra engine but as far as I know it was running inside IE only.

Re: First "official" NodeJS build on Windows

#15

Post by andypants » Wed, Jul 20, 2011, 12:44 PM UTC

wildmXranat wrote: post #13

Just throwing it out there, but what is the real reason behind making it windows friendly? Do developers want it or is it done with intentions to make it more appealing for corporate absorption?

Well... windows is a pretty popular operating system.

Re: First "official" NodeJS build on Windows

#16

Post by xtian » Wed, Jul 20, 2011, 12:56 PM UTC

davej wrote: post #4

mirrorskin wrote: post #2

Did anyone manage to get npm up and running on Windows yet?

No, there are still a number of issues with NPM support on windows. Isaacs talks about them on the latest NodeUp podcast: http://nodeup.com/

Check out ryppi for bare-bones package installation, though: https://github.com/japj/ryppi

Re: First "official" NodeJS build on Windows

#17

Post by [deleted] » Wed, Jul 20, 2011, 1:05 PM UTC

wildmXranat wrote: post #13

Just throwing it out there, but what is the real reason behind making it windows friendly? Do developers want it or is it done with intentions to make it more appealing for corporate absorption?

[deleted]

Re: First "official" NodeJS build on Windows

#18

Post by hvs » Wed, Jul 20, 2011, 1:17 PM UTC

deskamess wrote: post #14

MatthewPhillips wrote: post #10

Earlier quoted context omitted.

Why? If you use someone else's library there's going to be a dll associated. Node doesn't have any dependencies.

Does a javascript engine like V8 have to be installed separately to avoid dependency issues? Microsoft has the Chakra engine but as far as I know it was running inside IE only.

It's compiled into Node.

Re: First "official" NodeJS build on Windows

#19

Post by RyanMcGreal » Wed, Jul 20, 2011, 1:18 PM UTC

rbanffy wrote: post #7

Unless you are deploying on Windows, why not run it under cygwin? You may end up with a lot of silly problems with file paths, case insensitivity and any other "impedance mismatch" between your development environment and whatever server the workload will run on. I did a lot of Django development on Windows and Cygwin saved me a whole lot of pain.

I just tried to install node on cygwin and it failed with this error:

------

src/uv-cygwin.c:33: error: ‘CLOCK_MONOTONIC’ undeclared (first use in this function)

src/uv-cygwin.c:33: error: (Each undeclared identifier is reported only once

src/uv-cygwin.c:33: error: for each function it appears in.)

make[1]: * [src/uv-platform.o] Error 1

Re: First "official" NodeJS build on Windows

#20

Post by rbanffy » Wed, Jul 20, 2011, 1:25 PM UTC

RyanMcGreal wrote: post #19

rbanffy wrote: post #7

Unless you are deploying on Windows, why not run it under cygwin? You may end up with a lot of silly problems with file paths, case insensitivity and any other "impedance mismatch" between your development environment and whatever server the workload will run on. I did a lot of Django development on Windows and Cygwin saved me a whole lot of pain.

I just tried to install node on cygwin and it failed with this error: ------ src/uv-cygwin.c:33: error: ‘CLOCK_MONOTONIC’ undeclared (first use in this function) src/uv-cygwin.c:33: error: (Each undeclared identifier is reported only once src/uv-cygwin.c:33: error: for each function it appears in.) make[1]: * [src/uv-platform.o] Error 1

I have abandoned Windows again a couple years back, but, from my experience, most stuff that compiles cleanly under Linux, compiles cleanly under Cygwin. Do you have the required libraries? What did configure say? Can you try an older version (one known to work) to see if it compiles?