Repository navigation
What source files are built into node binary, and what are not? #6605
Description
Activity
@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.
@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.
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