Skip to content

No headers for crypto and ssl prebuilt libraries #255

Open
@aardvarkk

Description

@aardvarkk

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions