Rohit,
> Which of these modules are recommended for use?
I haven't used Qt or GTK with Node, so I can't give any recommendations
there...
There may be some alternatives: it looks like there are bindings for
wxWidgets, OpenVG and some OpenGL-related libraries (GLFW, GLEW and SDL).
Though OpenG
..but doesn't that also imply adding ninja as dep? All npm projects using
node-gyp might be affected (goes without saying, I guess). Possibly also
want to rethink the 'configure' phase. I've followed GN from a distance and
are willing to give it a whirl if its considered worth exploring.
On Wed
On Tue, Jul 8, 2014 at 9:22 PM, Simon Vincent wrote:
> Will node.js work on other hardware platforms other than X86 and ARM?
> If I managed to get it to compile for microblaze would it work or would I be
> wasting my time?
Just making it compile won't do you much good. V8 (the JS engine) is
a ru
As far as I can see `ninja` is still one of the build tools that could be
used with the build system.
I was just talking about a "transition stage", which will happen if we will
decide to move to GN.
On Wed, Jul 9, 2014 at 9:07 AM, Johan Bergström wrote:
> ..but doesn't that also imply adding
On Wed, Jul 9, 2014 at 2:56 AM, Johan Bergström wrote:
> It's pretty clear that Google is moving away and effectively abandoning Gyp
> at the end of this year. That means that everything within chromium (v8 and
> zlib is the only stuff that would affect node, right?) will be built by gn.
> Reading
One path to explore:
Use edge
https://github.com/tjanczuk/edge
Run .NET and Node.js code in-process on Windows, MacOS, and Linux
and script .NET WinForms or other types, to build desktop application.
Ummm. I don't know how to attend a .NET event from JavaScript (ie click
on button)
Angel "Ja
GN, Generate Ninja, is a pretty cool project, actually.
I actually always wondered: We have a scripting engine. Why do we rely on
Python for GYP, if we have NodeJS? Is there no gyp replacement in node itself?
Its something that I just never understood... Since the only people that build
from so
Am 09.07.2014 um 20:40 schrieb mscdex :
> On Wednesday, July 9, 2014 2:06:53 PM UTC-4, Ingwie Phoenix wrote:
> I actually always wondered: We have a scripting engine. Why do we rely on
> Python for GYP, if we have NodeJS? Is there no gyp replacement in node itself?
>
>
> I would think the prob
On Wed, Jul 9, 2014 at 9:23 AM, Ingwie Phoenix
wrote:
> I actually always wondered: We have a scripting engine. Why do we rely on
> Python for GYP, if we have NodeJS? Is there no gyp replacement in node
> itself? Its something that I just never understood... Since the only people
> that build fro
On Wednesday, July 9, 2014 2:06:53 PM UTC-4, Ingwie Phoenix wrote:
>
> I actually always wondered: We have a scripting engine. Why do we rely on
> Python for GYP, if we have NodeJS? Is there no gyp replacement in node
> itself?
>
>
I would think the problem would be when you're building from sour
This (no touch) is my current position as well -- but whatever
choice/decision is made is going to have to stick around for a long while.
Here's my thoughts so far:
- I don't particularly care about using python or not and I don't think
that discussion is beneficial to this thread.
- node-gyp
Hi Simon,
I looked into a different approach of putting JS on a FPGA by writing a JS
interpreter in a high-level-language to VHDL toolchain. Sadly, the low
clock speed of the FPGA makes interpreting JS painfully slow and it was
impractical. Dealing with timed logic and I/O also proved to be o
12 matches
Mail list logo
