Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Define WIN32_LEAN_AND_MEAN conditionally.
Fixes: #823 PR-URL: #824 Reviewed-By: Bert Belder <[email protected]>
- Loading branch information
90078ec
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A question unrelated to that commit, but rather the whole file: Can this mechanism theoretically be ignored on newer versions of node? This would probably just affect some users prior to 4.X right? Or is it integral to addon compilation?
90078ec
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@eljefedelrodeodeljefe: To my understanding it's needed with any version of node to support to use renamed node.exe and/or iojs.exe. As long as you (and the users of your native addon) keep using only node.exe it's not needed to use this mechanism (not even for older node versions).
In one of my projects (where I can't use node gyp for some unrelated reason) I skipped adding win_delay_load_hook.c in my build setup. Reason was that adding the linker switch /DELAYLOAD caused linker errors during import of some vtables once I added more and more code using node/nan/v8 APIs.
Seems to be related to the delayload constraints documented at https://msdn.microsoft.com/en-us/library/yx1x886y.aspx
90078ec
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Flarna okay. That's what I thought and thats reassuring. I'll try going without it. And thanks for the link!!