New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 919495 link

Starred by 3 users
Status: Untriaged
Owner: ----
Cc:
█ dstockwell@chromium.org
█ raymes@chromium.org
dpranke@chromium.org
thakis@chromium.org
dschuff@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task



Sign in to add a comment

add a toolchain to gn for wasm target

Project Member Reported by jochen@chromium.org, Jan 7 
in the end, it should be possible to build ink (https://github.com/google/ink) directly in a chrome checkout, instead of building it in google3 and importing the wasm binary into chrome.

Comment 1 by gbeaty@chromium.org, Jan 7

Cc: dpranke@chromium.org
Components: -Infra>Client>Chrome

Comment 2 by thakis@chromium.org, Jan 8

Cc: raymes@chromium.org dschuff@chromium.org
+dschuff raymes, with whom I discussed this a bit in an unrelated context too.

For the compiler, we need to use the regular clang package we bundle (which can generate wasm output). For bindings, emscripten provides something that works short-term, but long-term it'd be good if wasm offered a standalone working thing in llvm without deps on emscripten for bindings and binaryen etc.

I toyed with a proof of concept a while ago at https://chromium-review.googlesource.com/c/chromium/src/+/1282394 .
►

Sign in to add a comment