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
I have a Cocos project that was trying to include a copy of crypto. It seems, though, that I'm unable to use my own version of the crypto library because it conflicts with the Cocos version. It seems the Cocos version is relatively recent, but since I don't have the header files for it I can't make sure my code is using the same calling conventions as the prebuilt library.
Why aren't the headers for crypto and ssl packaged up in the external dependencies? Why are these prebuilt libraries packaged up into curl rather than just having Cocos depend on openssl separately?
The text was updated successfully, but these errors were encountered:
I have a Cocos project that was trying to include a copy of crypto. It seems, though, that I'm unable to use my own version of the crypto library because it conflicts with the Cocos version. It seems the Cocos version is relatively recent, but since I don't have the header files for it I can't make sure my code is using the same calling conventions as the prebuilt library.
Why aren't the headers for crypto and ssl packaged up in the external dependencies? Why are these prebuilt libraries packaged up into curl rather than just having Cocos depend on openssl separately?
The text was updated successfully, but these errors were encountered: