Can't build POP on a case sensitive file system about pop HOT 14 CLOSED

Tell me if there's any issue with the code or the podspec for AGGeometryKit+POP. :)

Den 16. mai 2014 kl. 17:39 skrev slizeray [email protected]:

Hey,

I can't build my projects with cocoa pods
For instance AGGeometryKit+POP,I keep getting the error:

.../AGGeometryKit-POP/Demo/Pods/pop/pop/POPAnimationExtras.h:12:9: 'POP/POPDefines.h' file not found

In addition, it looks like you are using inconsistently internal imports "...h" and library imports <...h>

For instance

#import in POPLayerExtras.h
and
#import "POPDefines.h" in PopCGUtils.h

Thanks ahead,

Stéphane

/cc @orta

—
Reply to this email directly or view it on GitHub.

from pop.

Interesting. Pop uses internal imports for private header and implementation files, library imports for all public files. I'm not intimately familiar with CocoaPods, but it seems like we should be able to make it work. Is everybody encountering this issue or is this an isolated report?

from pop.

I was able to successfully install AGGeometryKit+POP in an empty Xcode project. The Podfile I used:

platform :ios, '7.1'
pod 'AGGeometryKit+POP', '~> 0.1'

My import statements:

#import <POP/POP.h>
#import "POPAnimatableProperty+AGGeometryKit.h"

@slizeray can you confirm if the above work for you?

from pop.

Unfortunately I still can't build. I followed exactly what you did...

Here is the error message
.../Test/Pods/pop/pop/POPAnimationExtras.h:12:9: 'POP/POPDefines.h' file not found

Thanks ahead !

Stéphane

/cc @orta

from pop.

I would make sure you're using a standard set of compiler flags in the project importing files from <POP/….h>. If you manually adjust the include paths, it could override the defaults that Pop depends on.

from pop.

Please reopen this issue.
I guess your filesystem is NOT case sensitive.
On a case sensitive file system, you can't use POP.
You don't follow import rules.
Because your project is under "pop" (lower case) ALL your imports should look
#import <pop/POP.h> and NOT #import <POP/POP.h>

Please correct all your source code accordingly

Thanks ahead,

Stéphane

/cc @orta

To test if your filesystem is sensitive or not do the following:
touch abc1
touch abC1
ls ab*

Interpreting Results
1 file - case insensitive
2 files - case sensitive

from pop.

Or rename the directory pop and update the config files accordingly....

from pop.

Makes sense. Thanks for the extra information. We should definitely support case sensitive filesystems.

from pop.

Should it be POP, Pop or pop? I find different usage all over the place :)

from pop.

Ha. Good question. These are the rules I've been following:

1. 'pop' - marketing name for project
2. 'Pop' - marketing name in context of sentence
3. 'POP' - Obj-C namespace prefix

Use the one that feels right, the rest will follow. In this case, 3 tips me in favor of renaming the filesystem folder to all uppercase.

from pop.

Any Progress? I am eager to use pop...

from pop.

You should be able to make the adjustments above to your local copy before this is fixed in the main repository. Hopefully that can unblock you and let you start adopting Pop without any extra delay.

from pop.

@slizeray Let me know if this pull request works for you.

from pop.

@kimon, @grp - see pull request for explanation on why 'pop' is a better option than 'POP'

from pop.