-
-
Notifications
You must be signed in to change notification settings - Fork 8
analysis: add cmake toolchain analysis #9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: Michaël Zasso <[email protected]>
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.
LGTM
Co-authored-by: Michael Dawson <[email protected]>
|
||
* There seems to be positive reception at the idea of cmake for native modules, | ||
having the same build system for building Node.js and its native modules | ||
* It is already possible to build node-addon-api based native modules with cmake. |
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.
This is true for every build toolchain and also API (not just node-addon-api) so how valuable is this observation as a comparison to other toolchains?
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.
It is one that I know people have already been using and has been tested out/validated.
this only refers to building Node.js itself, not addons. An analysis of options for addons might be done in the future
This analysis is based on information gathered on
nodejs/TSC#901. We still need to collect more
information, especially in currently supported platforms and toolchains
(including minimum version for both). Consolidating the information here so
it's easier for us to iterate on it.