You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way the script is currently it does not work (anymore). I'm aware
of two issues with the current setup:
1. emsdk underneath installs and uses Node JS and the version of Node JS
is not pinned by the script and isn't tied to the version of the SDK
used.
As a result, emsdk moved to a newer version of Node JS than the one
that was probably used when the scripts were created. This new
version (it seems, the version currently being used is 18.20.3)
requires a relatively fresh version of glibc which just isn't
available in Ubuntu Bionic used as a base image. That results in
obscure errors from CMake (see
proxy-wasm#170)
2. for whatever reason, the version of the protobuf static libraries
currently in the repo, don't seem to work. I don't really know
how the issue happened, but there were at least 2 users that faced
the problem (see
proxy-wasm#161).
To resolve the first issue, we have a bunch of options:
1. Fix the version of emsdk
2. Fix the version of Node JS
3. Update the version of glibc
I figured I can combine options 1 and 3 together for the following
reasons:
1. Fixing the version of emsdk fixes the problem
2. The problem arised from the fact that the versions of software
used in the build script are a bit old, so an update might be
in order, even though we have other solutions to the problem.
> NOTE: It's my understanding that fixing emsdk version should also
> pin Node JS version, so if we deploy option 1, option 2 seem
> redundant.
For the second problem, I think there is only one ultimate solution
- not store binary artifacts in the repository and instead build
them from the sources in the repo.
It seems that in the past there was a concern that building protobuf
libraries takes a long time - it's still certainly the case. However,
I think we can compensate for that in two ways:
1. Drop WAVM - it does not seem like WAVM is still needed (the project
itself appears to be dead and hasn't had any updates for at least 2
years), but also one of the comments in
proxy-wasm#158, that
removed the WAVM from the docs, also suggests that three doesn't
seem to be a good reason to keep WAVM in the SDK build script.
2. Take advantage of potential hardware threads in the system when
calling make - most laptops or servers these days have multiple
cores, so if we have to build protobuf libraries twice, we can
speed it up by using more cores.
With all those changes made, the build time adds up to something like
32 minutes on my laptop, compared to the 48m without building
protobuf libraries from sources (and without adding -j option to make).
So I think the additional time spent on building protobuf library is
compensated by other changes.
Signed-off-by: Mikhail Krinkin <[email protected]>
0 commit comments