"config.h" not found (CocoaPods+iOS7) #124

Closed
jchatard opened this Issue Aug 13, 2013 · 6 comments

Comments

Projects
None yet
2 participants
@jchatard
Contributor

jchatard commented Aug 13, 2013

Hi,

I'm working on iOS 7, using Xcode 5 (preview of course), and when I compile my project, I get this error:

Mantle/metamacros.h:13:10: fatal error: 'config.h' file not found

Using :head for the pod.

Any idea?

Thanks,
Jérémy

@jspahrsummers

This comment has been minimized.

Show comment Hide comment
@jspahrsummers

jspahrsummers Aug 13, 2013

Member

This would only occur if HAVE_CONFIG_H is defined somewhere in your project or in a podspec. I can't reproduce this when building Mantle by hand, so it must be a CocoaPods or configuration issue.

Member

jspahrsummers commented Aug 13, 2013

This would only occur if HAVE_CONFIG_H is defined somewhere in your project or in a podspec. I can't reproduce this when building Mantle by hand, so it must be a CocoaPods or configuration issue.

@jchatard

This comment has been minimized.

Show comment Hide comment
@jchatard

jchatard Aug 13, 2013

Contributor

Hmm, yes this was related to YAML.framework.

Contributor

jchatard commented Aug 13, 2013

Hmm, yes this was related to YAML.framework.

@jchatard jchatard closed this Aug 13, 2013

@jchatard

This comment has been minimized.

Show comment Hide comment
@jchatard

jchatard Aug 13, 2013

Contributor

Hmm, after digging around, LibYAML is using the same condition.

Would it be possible to kind of namespace HAVE_CONFIG_H like MANTLE_HAVE_CONFIG_H so that this solves the issue? Or would that lead to problem for Mantle?

Contributor

jchatard commented Aug 13, 2013

Hmm, after digging around, LibYAML is using the same condition.

Would it be possible to kind of namespace HAVE_CONFIG_H like MANTLE_HAVE_CONFIG_H so that this solves the issue? Or would that lead to problem for Mantle?

@jchatard jchatard reopened this Aug 13, 2013

@jspahrsummers

This comment has been minimized.

Show comment Hide comment
@jspahrsummers

jspahrsummers Aug 13, 2013

Member

We can simply remove the check, since it's not actually useful, but it's nonetheless being caused by something funky in your configuration. HAVE_CONFIG_H shouldn't be defined globally unless there's a config.h header that all files can see.

Member

jspahrsummers commented Aug 13, 2013

We can simply remove the check, since it's not actually useful, but it's nonetheless being caused by something funky in your configuration. HAVE_CONFIG_H shouldn't be defined globally unless there's a config.h header that all files can see.

@jchatard

This comment has been minimized.

Show comment Hide comment
@jchatard

jchatard Aug 13, 2013

Contributor

Yeah, I'm usine LibYaml which installed via CocoaPods raises this issue. I'll create a pull request tomorrow of you wish.

Thanks,
Jeremy

Contributor

jchatard commented Aug 13, 2013

Yeah, I'm usine LibYaml which installed via CocoaPods raises this issue. I'll create a pull request tomorrow of you wish.

Thanks,
Jeremy

@jspahrsummers

This comment has been minimized.

Show comment Hide comment
@jspahrsummers

jspahrsummers Aug 13, 2013

Member

Sure, that'd be helpful. Thanks!

Member

jspahrsummers commented Aug 13, 2013

Sure, that'd be helpful. Thanks!

jspahrsummers added a commit that referenced this issue Aug 13, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment