-
Notifications
You must be signed in to change notification settings - Fork 948
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
Can't Build Project for Release #46
Comments
I "fixed" this problem by going to my target's 'Linked Frameworks and Libraries' section and adding TessearctOCR.framework to it. That fixes the archiving issue, but the warnings stay there, annoyingly enough. |
I guess, that you added .a files to "Compile Sources" of a release target. |
I am having the same warnings but instead of using the TessearctOCR.framework directly I am using Tesseract as a CocoaPod. This then results on a linking error:
Undefined symbols for architecture armv7:
"_OBJC_CLASS_$_Tesseract", referenced from:
objc-class-ref in xxxx.a(xxx.o)
ld: symbol(s) not found for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)
I tried to remove the .a files from "Compile Sources" but to no avail. Do you have any further insight on what could be the issue here? |
These issues should be fixed by #71, which is now a part of CocoaPods release 3.1.1. Update your podfile to use it:
I'll close the issue for now, but feel free to reopen it if it's still not working for you. |
Hi, I have the same issue with the latest pod version (3.1.1):
So it seems this issue was not resolved by #71. |
@manenko, I just created a brand new iOS 8.1 project in Xcode 6.1.1, added this line to a blank Podfile:
ran I have a theory about what might be going wrong for you, but before we get to that, can you let me know the following things?
|
I apologize for the false alarm. I changed Podfile to use 3.1.1 in project AAA, but I thought that I did that for project BBB. So BBB used old version of the library and I reported this. Now when I changed Podfile for project BBB use 3.1.1, it compiles without any warnings. I'm very sorry for the false alarm. |
No worries! Let us know if you run into any other issues. Also we just released a new CocoaPods update (really just a version bump, see #74), but now if you leave off the specific version in the Podfile it will use the latest version of the library (now 3.4.0). |
Hi Kevin, The framework files in the Pods project are red, because they refer to /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS7.1.sdk/System/Library/Frameworks/Foundation.framework Thank you! |
@pwansch, I created a new project using the same steps as you did, and although I also see those items in red like you do, building and running the project works perfectly fine (see screenshot below). The only red items that refer to the iOS7.1-related path are Foundation.framework and UIKit.framework in Pods/Frameworks/iOS. This seems to be an issue with CocoaPods itself, but I can assure you that everything will still build correctly regardless. Here's the related issue on CocoaPods: CocoaPods/CocoaPods#2324 Screenshot of the 3.4.0 Cocoapod running fine using the same version of Xcode as you: |
Thank you @kevincon. This perfectly answered my question. |
I have an app using Tesseract which runs just fine in development, but when I want to archive it, I get a series of warnings:
And, of course, archiving fails due to
undefined symbols for architecture
.Any tips on this?
I've read this can be caused by having the wrong files in "Compile Sources", but as far as I can tell, I only have .m files and core data models in there.
The text was updated successfully, but these errors were encountered: