-
Notifications
You must be signed in to change notification settings - Fork 63
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
Check SQLite.framework reference -- iOS? #10
Comments
Nice catch. I wonder if some of the changes in #8 fixed it? |
@ruslanjabari just opened: #8. I'm taking a look at it now - in a very broken state locally 😅 so it's taking a few. Any opinions on Cocoapods vs Carthage vs. Swift Package manager vs. local? |
Can confirm, #8 fixed me (and also fixed some resulting code signing issues I was having and hadn't started to debug yet). 🙇♂️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
I had some trouble getting an initial build to work in Xcode after cloning
SQLite.swift
.I had to update the (relative path) reference to SQLite.swift from within Xcode (took an embarrassingly long time because I'm not a daily Xcode user...) but then I ran into another issue: a build failure due to a missing build directory:
Note:
Debug-iphoneos
- I don't have anything except the macOS SDKs installed.I poked around on the internet and tried to read between the lines, but ultimately fixed it by deleting
SQLite.framework
in therem
targetBuild Phases
section under bothLink Binary with Libraries
andEmbed Frameworks
and re-adding it, taking care to add the macOS SDK, not the iPhone version. After that my builds succeeded.Screenshot:
Additional Info
I'm not sure if it's portable, but the relevant
git diff
in my .xcodeproj file is:Other
OMG thank you for posting this. I've been meaning to take a poke at it, but it's much easier to have a skeleton to work inside since I'm not a Swift/Objective-C user normally.
The text was updated successfully, but these errors were encountered: