-
|
I'm upgrading an Xcode project that was pretty old to the latest Swift 6, Xcode 16.2, macOS 15.3 on an M3 and now using the latest GRDB with the Swift Package Manager. I've hit a linking problem and I'm stuck, not knowing where to look. GRDB previously was a pod/framework but is now under package management. Everything compiles, but I hit this error: ld: warning: search path '/Users/hankm/Library/Developer/Xcode/DerivedData/Trail_Pro-cwsoiakqdyfzbqcclufludioatsv/Build/Products/Debug-iphonesimulator/GRDB.swift' not found then: Ld /Users/hankm/Library/Developer/Xcode/DerivedData/Trail_Pro-cwsoiakqdyfzbqcclufludioatsv/Build/Products/Debug-iphonesimulator/Trail\ Pro.app/Trail\ Pro.debug.dylib normal (in target 'Trail Pro' from project 'Trail Pro') ... Lots and lots of options and finally ... ld: warning: search path '/Users/hankm/Library/Developer/Xcode/DerivedData/Trail_Pro-cwsoiakqdyfzbqcclufludioatsv/Build/Products/Debug-iphonesimulator/GRDB.swift' not found Should it be looking for a framework with the package manager? Is this some kind of leftover from the previous project environment? I've checked all the settings and GRDB is listed as a dependency, is listed in "Frameworks, Libraries and Embedded Content", and in Build Phases is listed in "Link Binary with Libraries" Not sure what else to check. Any suggestions appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Hello @hankster. I suggest to perform a project cleanup, and why not deleting your app folder in |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your suggestions @groue, but they didn't work. The project is no longer using any Pods, and after additional checking I started deleting all the Pod references I could find. In particular, three items in the Build Phases did some Pod scripts and after deleting those I was able to get the build to succeed. It seems that Xcode does not properly clean up Pod litter or I didn't delete the Pod references properly. In any case, the app is now running and I'm able to start debugging. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for sharing your solution 👍 |
Beta Was this translation helpful? Give feedback.
Thank you for your suggestions @groue, but they didn't work.
The project is no longer using any Pods, and after additional checking I started deleting all the Pod references I could find. In particular, three items in the Build Phases did some Pod scripts and after deleting those I was able to get the build to succeed.
It seems that Xcode does not properly clean up Pod litter or I didn't delete the Pod references properly. In any case, the app is now running and I'm able to start debugging.