Made some progress on this with the raw loading code once you have a dll assuming you statically link against node.exe using the node.lib that is generated for it.

https://github.com/bmeck/node/tree/windowsdll

This required a small patch to v8.h unfortunately so that it exported when being statically linked into an executable.
However, there is a problem currently. All dll export methods I have tried (dynamic and static permutations) do not want to use members of templated classes from node.exe, see:

http://msdn.microsoft.com/en-us/library/esew7y1w.aspx
http://stackoverflow.com/questions/2132747/warning-c4251-when-building-a-dll-that-exports-a-class-containing-an-atlcstring

The solution appears to be to export all template instanciations:
http://support.microsoft.com/kb/168958

Does this sound sane? I am not familiar enough w/ linking against templated classes in windows to determine if this might cause problems with types that may be templated in plugins rather than node.exe (ObjectWrap...).

Uh oh!

Add .node/.dll support for windows #1746

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions