Closed schultezb closed 5 days ago
I believe this is fixed in 3.1.60 from https://github.com/emscripten-core/emscripten/commit/1336355ab0bc040c9122ef8b93aae40366920fce
Thank you, I can confirm that this particular bug is fixed in 3.1.61.
We're experiencing different issues with that version such as a LLVM frontend crash with some particular code of ours but that is outside of the scope of this issue.
We encounter a regression after updating Emscripten from 3.1.49 to 3.1.60. Binding custom types as field of an
emscripten::value_object
now triggers a compilation error'uses_ref_count' is a private member of 'emscripten::val'
. Binding native types as field works as expected. Manually editing val.h to makeval::uses_ref_count()
public instead of private solves the issue but is obviously a hack.Details We use a couple of custom types inheriting from
emscripten::val
so that we can nicely wrap/convert complex C++ types to JS types/objects that can be used more naturally on the JS side. We then bind them tovalue_objects
so that we don't need to worry about lifetime issues.Minimally reproducable example:
Please include the following in your bug report:
Version of emscripten/emsdk:
Failing command line in full: