-
Notifications
You must be signed in to change notification settings - Fork 113
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
ARC support? #26
Comments
That particular variable is going away soon, because it didn't do what I thought it would. Are there any other ways compiling with ARC breaks? I suppose we will use ARC in the future, but at the very least Kitten should be compatible with an ARC environment. |
As far as I can say, there's only the double pointers, but I think they appear in other PDFKitten classes as well |
you can switch off ARC for the files of this project: |
@abc-xyz Yes, I know that, but PdfKitten, at least the version I use, doesn't support ARC and doesn't work with -fobjc-no-arc together either (see my original mail) |
@fuggly I ran into this same thing -- could not get it to work. Then I discovered: Wrong flag! The one you have mentioned here is incorrect. Using the correct one, -fno-objc-arc, works fine. |
@andrewhoyer @KurtCode sorry it took me half a year to respond, but yes, you're right Andrew. PdfKitten compiles fine if I use the correct flags. My bad! Sorry everyone and thanks for all :-) |
Hiyas
I don't think this can be considered an issue, but is it planned to support ARC in the future? The problem is, that even in a project where ARC is enabled and PdfKitten is excluded, a project still doesn't compile because of things like NSMutableString** rawTextContent (Scanner.h) for example. Every ARC enabled project gets freaky when it should compile this class (even if PdfKitten is excluded).
The text was updated successfully, but these errors were encountered: