Piotr Sikora
Piotr Sikora
It looks that `sha256sum` was removed (or possibly replaced with `gsha256sum`?), which broke cache-key evaluation: ``` echo "::set-output name=uniq::$(bazel query --output build //external:v8 | grep -E 'sha256|commit' | cut -d\"...
Currently used images are a few years old (`ubuntu-20.04`, `macos-11`, `windows-2019`) and include even older versions of toolchains, which may result in build failures. cc @mpwarres
LLVM can be built using Bazel (see: https://github.com/llvm/llvm-project/tree/main/utils/bazel), which would be cacheable. Currently, WAMR JIT and WAVM tests are building LLVM using CMake, which isn't cacheable and results in multi-hour...
Previously, both: embedding C/C++ application and the library had to be built using the same DEBUG define, because vec::make_data() and vec::free_data() were declared in the implementation when built with DEBUG...
Signed-off-by: Piotr Sikora
Signed-off-by: Piotr Sikora
I expect those `BUILD` rules to work: ``` perl_xs( name = "CacheMemcachedFastXS", srcs = ["Fast.xs"], defines = [ "VERSION=\"0.26\"", "XS_VERSION=\"0.26\"", ], output_loc = "arch/auto/Cache/Memcached/Fast/Fast.so", textual_hdrs = ["ppport.h"], typemaps = ["typemap"],...
Note that OpenSSL won't be able to support this change for a while (see: #149).
This was requested in yesterday's meeting, so adding it mostly for tracking. Note that OpenSSL doesn't have QUIC APIs (and it's unlikely to have them for the next few years,...