node
node copied to clipboard
Document the build configuration options for Nodejs binaries
What is the problem this feature will solve?
It would be helpful in https://github.com/nodejs/node#release-types or https://github.com/nodejs/node/blob/main/BUILDING.md if there could be documentation of whether the provided binaries by
nodejs.org
use any additional configuration options when building Nodejs, or if everything is built using the default options.
From https://github.com/nodejs/node/blob/main/.github/workflows/build-tarball.yml#L56, it looks like only the default options in ./configure
and make
(beyond the option for the creation of the tar) are used when creating the artifacts, but it would be good to have confirmation. If that is the case, could a line be added to public facing documentation?
I would like to ensure when I perform my own build from source, that we are using the same configurations as the publicly available pre-compiled binaries. Thanks!
Sorry if I missed this somewhere else, but I wasn't able to find it.
What is the feature you are proposing to solve the problem?
Updated documentation.
What alternatives have you considered?
Developers could find this through the code, but it is hard to determine and verify without previously working on Node.
@nodejs/build I think the answer is "default config"?
If that is the case, could a line be added to public facing documentation?
Do you have a suggestion of where in the public facing documentation this would be the most discoverable?
I see you have made a few suggestions above in terms of the docs, any particular section?
There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment.
For more information on how the project manages feature requests, please consult the feature request management document.
@BethGriggs FYI as this might related to some of the work you were thinking about related to provenance and SBOMs
There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment.
For more information on how the project manages feature requests, please consult the feature request management document.
There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment.
For more information on how the project manages feature requests, please consult the feature request management document.