What source files are built into node binary, and what are not?

[IlyaBiryukov]

• Version: 4.4.3
• Platform: Windows

We're evaluating shipping node as a component in some of our products. As part of that, we're performing intellectual property scan of the node source files. For the scan it's critical to know whether the source files actually end up in node executable bits and will be part of distribution, and when they do not, i.e. when they're only related to tests, build tools, samples, docs, etc.

Is there a doc or folder map that can help distinguish whether the files are shipping in node bits or not?

Thanks,
Ilya

[ghost]

Not to hijack this issue but I have a similar but different question. I'm running dumpbin /EXPORTS on the node binary on Windows and it seems you only export V8 and libuv functions for addons to link against. On Unix systems the binary exports OpenSSL, libz, V8 and libuv. I cannot get my cross-platform addon to compile on Windows due to undefined symbols (OpenSSL functions). What gives and how am I supposed to build on Windows? Why aren't you properly exporting the same functions as on Unix? It makes it impossible to support Windows.

[mscdex]

@alexhultman You'll probably want to follow #6274 for that. I think it's not implemented yet because it's not easy to do on Windows from what I understand.

[bnoordhuis]

@IlyaBiryukov node.gyp in the top-level directory and the *.gyp(i) files it includes ultimately decide what source files end up in the final binary; grep them for 'sources' and 'action' fields. As a rule of thumb: files in deps/, src/ and lib/ are compiled in, files in other directories are not.

Hope that answers your question. I'll close the issue but feel free to ask follow-up questions.