-
Notifications
You must be signed in to change notification settings - Fork 514
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
OS X Support Broke Carthage #140
Comments
If you copy-pasta the defines into each class that use them rather than just the import of |
@justin thanks for looking into it! Let me know if I can help in any way. |
Maybe @maicki can chime in with some thoughts since he spearheaded the OS X support. |
@justin @garrettmoon Can we close that issue due to: #160 ? |
Let me dig into it today. I'll report back. |
This branch fixes it I believe. https://github.com/justin/PINRemoteImage/tree/fix/osx-conditionals I updated the conditionals to be more explicit and added an import of Computers! |
Computers! Mind putting up a pull request? |
Yessir! #164 |
Landed! |
Whoooo. Would be nice if it became a 2.1.1 so we could get back on mainline. We're still tagged at 1.2.3 |
Absolutely, I'll try and get this released over the weekend (ping this thread if I forget). |
Published 2.1.1 |
On lower end devices most operations end up being empty trash operations. That issue needs to be addressed, but in the meantime, lets bump this number up.
When I try to use a freshly built copy of the framework from
master
, it gets mad about thePINImage
defines saying it can't find them.It builds fine in the
PINRemoteImage
project, but importing it into a third-party iOS app causes tons of errors around the define breaking down.I wonder if frameworks can't deduce the
#define
values? I can't really find any documentation to validate or invalidate this.The text was updated successfully, but these errors were encountered: