Skip to content

build: restore libplatform headers in distribution - #39288

Closed
jeroen wants to merge 1 commit into
nodejs:masterfrom
jeroen:libplatform-headers
Closed

build: restore libplatform headers in distribution#39288
jeroen wants to merge 1 commit into
nodejs:masterfrom
jeroen:libplatform-headers

Conversation

@jeroen

Copy link
Copy Markdown
Contributor

I maintain libnode/v8 bindings for the R programming language, which depend on libnode on most Linux distro's, e.g. r-cran-v8 in Debian/Ubuntu and R-V8 in Fedora.

Headers considered non-essential were removed in #37570, however the libplatform API is actually needed by external software initiating the v8 engine. See for example the upstream v8 hello world example: https://chromium.googlesource.com/v8/v8/+/refs/heads/main/samples/hello-world.cc

I have also asked upstream v8 if the API in question could maybe be moved to the top level v8-* headers, but they have not responded.

I hope it can be reconsidered to ship these headers, otherwise it will no longer be possible for us to build bindings for libnode, which would be very unfortunate, because they are widely used.

Headers considered non-essential were removed in #37570, however the libplatform API is actualy needed (and used) by external software initiaing the v8 engine, see for example https://chromium.googlesource.com/v8/v8/+/refs/heads/main/samples/hello-world.cc
@github-actionsgithub-actionsBot added build Issues and PRs related to build files or the CI. needs-ci PRs that need a full CI run. python PRs and issues that require attention from people who are familiar with Python. labels Jul 6, 2021
@richardlaurichardlau added the embedding Issues and PRs related to embedding Node.js in another project. label Jul 6, 2021
@richardlau

Copy link
Copy Markdown
Member

cc @nodejs/embedders

@targos

Copy link
Copy Markdown
Member

otherwise it will no longer be possible for us to build bindings for libnode, which would be very unfortunate, because they are widely used.

It's always possible for you to have your own copy of these headers.

That said, as the one who removed them and who does most of the work related to V8 updates, I'm okay with this change. The libplatform headers rarely have breaking changes.

@targostargos added the request-ci Add this label to start a Jenkins CI on a PR. label Jul 6, 2021
@github-actionsgithub-actionsBot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jul 6, 2021
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@targostargos added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. dont-land-on-v12.x labels Jul 7, 2021

@mhdawsonmhdawson left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM

targos pushed a commit that referenced this pull request Jul 11, 2021
Headers considered non-essential were removed in #37570, however the
libplatform API is actualy needed (and used) by external software
initiaing the v8 engine, see for example:
https://chromium.googlesource.com/v8/v8/+/refs/heads/main/samples/hello-world.cc
PR-URL: #39288
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@targos

Copy link
Copy Markdown
Member

Landed in c476bb8

@targostargos closed this Jul 11, 2021
targos pushed a commit that referenced this pull request Jul 11, 2021
Headers considered non-essential were removed in #37570, however the
libplatform API is actualy needed (and used) by external software
initiaing the v8 engine, see for example:
https://chromium.googlesource.com/v8/v8/+/refs/heads/main/samples/hello-world.cc
PR-URL: #39288
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@jeroen
jeroen deleted the libplatform-headers branch July 11, 2021 07:58
@targostargos mentioned this pull request Jul 13, 2021
codebytere added a commit to electron/electron that referenced this pull request Jul 14, 2021
jkleinsc added a commit to electron/electron that referenced this pull request Jul 15, 2021
* chore: bump node in DEPS to v16.4.2
* chore: update patches
* ci: run main and remote woa tests separately
* chore: bump node in DEPS to v16.5.0
* build: restore libplatform headers in distribution
nodejs/node#39288
* build: pass directory instead of list of files to js2c.py
nodejs/node#39069
* chore: various BoringSSL/OpenSSL upstreams
- nodejs/node#39136
- nodejs/node#39138
- nodejs/node#39054
* test: move debugger test case to parallel
nodejs/node#39300
* chore: fixup patch indices
* build: pass directory instead of list of files to js2c.py
nodejs/node#39069
Co-authored-by: electron-roller[bot] <84116207+electron-roller[bot]@users.noreply.github.com>
Co-authored-by: PatchUp <73610968+patchup[bot]@users.noreply.github.com>
Co-authored-by: John Kleinschmidt <jkleinsc@electronjs.org>
Co-authored-by: Shelley Vohr <shelley.vohr@gmail.com>
BlackHole1 pushed a commit to BlackHole1/electron that referenced this pull request Aug 30, 2021
* chore: bump node in DEPS to v16.4.2
* chore: update patches
* ci: run main and remote woa tests separately
* chore: bump node in DEPS to v16.5.0
* build: restore libplatform headers in distribution
nodejs/node#39288
* build: pass directory instead of list of files to js2c.py
nodejs/node#39069
* chore: various BoringSSL/OpenSSL upstreams
- nodejs/node#39136
- nodejs/node#39138
- nodejs/node#39054
* test: move debugger test case to parallel
nodejs/node#39300
* chore: fixup patch indices
* build: pass directory instead of list of files to js2c.py
nodejs/node#39069
Co-authored-by: electron-roller[bot] <84116207+electron-roller[bot]@users.noreply.github.com>
Co-authored-by: PatchUp <73610968+patchup[bot]@users.noreply.github.com>
Co-authored-by: John Kleinschmidt <jkleinsc@electronjs.org>
Co-authored-by: Shelley Vohr <shelley.vohr@gmail.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.buildIssues and PRs related to build files or the CI.embeddingIssues and PRs related to embedding Node.js in another project.needs-ciPRs that need a full CI run.pythonPRs and issues that require attention from people who are familiar with Python.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

@jeroen@richardlau@targos@nodejs-github-bot@cjihrig@mhdawson