Skip to content

assert.h conflict with Xcode use_headermap #150

@ph4r05

Description

@ph4r05

Hi,

I've been experiencing the following build problem after adding this library via cocoa pods.

The TrustKit contains assert.h file. XCode by default has
set USE_HEADERMAP=YES. It builds a mapping on the header files enabling simple imports without need to follow directory structure or set include paths.

My project is quite big and was build with this XCode settings enabled. I am also using another thirdparty library which includes the system <assert.h>. But after adding TrustKit the assert.h is ambiguous and conflicts with the system one. This causes my build to fail.

One workaround would be to set USE_HEADERMAP=NO but then I would have to refactor my whole project and use either relative import paths everywhere or configure all include paths.

I was wondering whether you could possibly rename this header file so it does not conflict with the system one.

Thanks!

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