-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
CocoaPods fix: Xcode 7.3 #380
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
Conversation
Imports the SDK based on current architecture. Fixes incompatibility problems for Xcode 7.3. Also includes link flag for convenience.
I've just missed arm64 compatibility. Works now fine with Xcode 7.2.1
Xcode 7.3 got more strict about SDK headers. We need to use multiple module maps to accommodate various platforms and we need to scope `requires` to accommodate various architecturers. Signed-off-by: Stephen Celis <[email protected]>
98a4cc0
to
8d2903b
Compare
@stephencelis any word on when this will be merged in? |
@gblotter Can you verify that it works for you and list the simulators/devices you tested? |
@stephencelis I can't... I rely on SQLiteCipher.swift... I'm trying to get a pod spec stood up in that project that I can submit a PR to you for... but it relies on this project. I've essentially applied this same fix to the SQLiteCipher.swift project but the spec won't/can't lint properly because of this issue in this project hasn't been merged into master. I can't point it to a branch, or else I'd test it that way... So I'm trying to wait patiently 😊 |
Hope to get some confirmations soon :) |
I'm getting lots of sqlite3 errors when installing the pod above. Im going from a frameworkless installation and dropping my iOS 7 support. |
@Hinken Can you provide much more detailed information on your situation? Is |
@stephencelis I can confirm that I'm seeing the same thing. One thing I noticed... Here are the contents of the SQLite.swift module file that is being generated:
No header import of the sqlite3 library |
I'm seeing the same thing as @gblotter |
Can someone provide much more detailed information around their setup? I'm at a loss troubleshooting this because it's working for me :( |
Same as the previous two people... Xcode 7.3, building for the iOS simulator... |
I have pod "SQLite.swift", pod install (I've also tried pod update, but same results) |
Can you paste the contents of |
Can you also try the CocoaPods 1.0.0 beta?
I wonder if this is fixed in newer versions. |
PODS:
DEPENDENCIES:
EXTERNAL SOURCES: CHECKOUT OPTIONS: SPEC CHECKSUMS: COCOAPODS: 0.39.0 |
Pods/Local Podspecs/SQLite.swift.podspec.json:
But my directory isn't showing a path for CocoaPods/*. Do you need to preserve the path? |
@stephencelis are you running the beta cocoapods?? |
@gblotter I meant the Podfile.lock, not the podspec. The path shouldn't need to be preserved. It's relative to the pod repo. |
@gblotter Yep. I think it may be required. |
Sorry, mine's still doing the deep fetch of master |
... updating to cocoapods beta ... |
I was using cocoapods 1.0.0.beta.4, and had the same errors as @gblotter. I have just upgraded to 1.0.0.beta.6 and now it works, but I had to completely delete the |
Okay. The deep fetch finally finished. I can build now with your branch. I can build for iOS Device and iOS Simulator. I can also seem to build for tvOS simulator (I get an error later on in my code since I haven't built it in a while). |
@stephencelis Since it seems that it was a bad Xcode upgrade for those that this branch didn't work for, is it okay to merge this in now? |
👍 Sounds good! |
Ahh, it seems like my build that works just fine locally is failing on CirlceCI now 😕
|
@cjwirth, did you try reinstalling (preferably not from the App Store) Xcode on that machine? |
@brandenr It's on CircleCI, I don't have access to the machine 😕 On my own machines, yeah, I always download the dmg version. |
@cjwirth Do you know what Xcode they're running? Those look a lot like the errors you get with Xcode 7.2 or a bad install of Xcode 7.3 |
I don't know how they are installing it, but I know that it is selecting it by doing
Which lists the same version I have installed too. But I don's suppose that would change from dmg/AppStore versions |
Ah. Based on "/Applications/Xcode.app/".. being in the header, I'm not sure that's going to work if they've named it Xcode-7.3.app |
Yep, it hit me literally 30 seconds ago as well... |
Well, no, because I just did that locally, and it just tells me "header can't be found." CircleCI still has Xcode 7.0 or something installed at |
Hi @stephencelis
I hope this is helping :-) |
@Souf-R, 0.9.2 doesn't support Xcode 7.3. You need to point at this branch or commit (if the branch has been deleted) |
@Souf-R You can point to master (this branch was merged). I'll be cutting a release shortly. |
Ok @stephencelis, I will wait for the release while I'm testing with my iPhone. |
Yes, 0.9.2 works with Xcode 7.3 when building for a device. I meant with a simulator and a device. |
Deleted my previous comment because it was unhelpful. But I've discovered something useful now. Currently, the module map for iOS has this inside it:
And it builds fine for device, but not simulator. However! If we move the I don't know much about module maps, but if it works on dmg Xcode and not AppStore Xcode, then it sounds like it's a bug in one of them. I don't know which is which, but for now I think it would be best to get it working in both. I'm going to see if I can get a setup where it only uses the module map for the current architecture. |
The App Store Xcode works for me and another. Just not everyone. |
Still noone can solve this error? |
@acrookston i don't see the answer there? how to solve my trouble. i've just updated cocoapods to 1.0 beta but the other errors have occurred |
@tom29 I believe that may have been merged in afterwards. Can you try pointing your Podfile to |
Follow my manual install method Sent from my iPhone
|
@stephencelis Tks. It works. |
This should hopefully fix issues #349 #378 and includes work from #379.
Please test on your platform and report if it works!
Will merge when things look good!