Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

assert.h conflict with Xcode use_headermap #150

Closed
ph4r05 opened this issue Nov 18, 2017 · 2 comments
Closed

assert.h conflict with Xcode use_headermap #150

ph4r05 opened this issue Nov 18, 2017 · 2 comments

Comments

@ph4r05
Copy link

ph4r05 commented Nov 18, 2017

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!

@nabla-c0d3
Copy link
Member

Good catch and this looks like the root cause of #148. We'll take care of it.

@nabla-c0d3
Copy link
Member

Fixed in 1.5.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants