POP-MCAnimate Pod does not build 'POP.h' file not found with <angled> includes; use "quotes" instead

Are you including POP as a sub pod? Either way, it won't build for me using cocoapods and xcode 7.

I get this error: Pod does not build 'POP.h' file not found with <angled> includes; use "quotes" instead

Dec 19 '15 18:12 slcott

It works for me. Did you run pod install?

Dec 19 '15 18:12 matthewcheok

Yes. The pod is installed.

My system has the pop pod installed for other targets in my workspace. Maybe that's why the compiler complains about all occurrences of #import <POP.h>. Perhaps it wants instead this: #import <pop/POP.h>.

Maybe my Podfile is incorrect. It looks like this:

target 'Carousel' do
    platform :ios, '9.0'
    pod 'RegExCategories'
    pod 'pop'
    pod 'POP+MCAnimate', '~> 2.0'
    link_with 'Carousel'
end

Dec 19 '15 19:12 slcott

POP+MCAnimate includes pop for you. You can omit that dependency.

Dec 19 '15 19:12 matthewcheok

If you need to include pop directly, maybe just include the source files directly to avoid problems.

Dec 19 '15 19:12 matthewcheok

Ok. well I wish you hadn't closed this issue immediately because I changed my podfile and have the same error. Please be patient.

target 'Carousel' do
    platform :ios, '9.0'
    pod 'RegExCategories'
#    pod 'pop'
    pod 'POP+MCAnimate', '~> 2.0'
    link_with 'Carousel'
end

I get the same error.

Dec 19 '15 19:12 slcott

The configuration in the demo project works for me. It might be something specific to your cocoapods configuration.

Dec 19 '15 19:12 matthewcheok

Found it. My Podfile has use_frameworks!. I included that like in the McAnimate demo project and that recreated the same issue I was having.

From the CocoaPods docs

Another difference is their file system representation: Frameworks are bundles, which basically means that they are directories, which have the file suffix .framework and Finder treats them mostly like regular files

So I guess that's why the compiler couldn't find the path for the imports. McAnimate currently supports static libraries but not dynamic frameworks? Can you add support for it? Maybe this is not the issue but other pods don't seem to cause issues with the use_frameworks! option.

Dec 19 '15 19:12 slcott

Might take me a while to get to this but feel free to submit a PR for this fix if you get to it sooner.

Dec 20 '15 00:12 matthewcheok

I doubt why we just don't change it to <pop/POP.h>