I think embind JS file comes in with the --pre-js directive, so the linking phase unfortunately does not see these symbols being added in. I can't remember outright if there is some problem with using --js-library for embind, although it would require a bit of rewrite of the embind .js file structure. At the moment it is safe to ignore those at least.
Jukka 2014/1/22 ShunXung Yang <[email protected]> > when I used emcc to compile cpp files, I got these warning messages. > The output js file is runnable. but I am not sure these warnings dose > matter or not. > > warning: unresolved symbol: _embind_register_class_function > warning: unresolved symbol: _embind_register_class_constructor > warning: unresolved symbol: _embind_register_class > warning: unresolved symbol: _embind_register_void > warning: unresolved symbol: _embind_register_bool > warning: unresolved symbol: _embind_register_integer > warning: unresolved symbol: _embind_register_float > warning: unresolved symbol: _embind_register_std_string > warning: unresolved symbol: _embind_register_std_wstring > warning: unresolved symbol: _embind_register_emval > warning: unresolved symbol: _embind_register_memory_view > > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
