Skip to content

Conversation

mmarchini
Copy link
Contributor

@mmarchini mmarchini commented Jan 30, 2022

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.

## Cons

* Other dependencies will need Node.js-maintained Bazel build files
* Currently support a limited set of platforms

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm curious which host platforms node supports and Bazel doesn't? Perhaps the Bazel team can ship more binaries.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's less about bazel running on the platform and more about V8 providing the configurations for those platforms or not (according to this comment the range of platforms supported by the bazel configs is only a subset of currently supported platforms with GN).


## Need more info

* Could V8 use Bazel instead of GN in their CI?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think @philwo is best suited to answer this.

@mmarchini mmarchini force-pushed the bazel-toolchain-analysis branch from 6b5def1 to 6b6db21 Compare January 31, 2022 01:12
Copy link
Member

@mhdawson mhdawson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants