Open michaeleggers opened 1 year ago
OK, I realized that those functions without ENET_API are internal, which makes sense. I am generating bindings for another language and it makes it a bit awkward to do this with internal symbols mixed with the interface.
Seems like you have answered your own question. So this issue can be closed?
Seems like you didn't read the second part of my message. It is still a bit harder to generate a binding if internal/external functions are mixed.
When building enet as a DLL functions like:
are not being exported because their linkage is not
ENET_API
butextern
.Is there a reason why certain functions are not ENET_API? Thank you :)