Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • In my case, I was seeing ld: library not found for -lswiftCoreImage for architecture x86_64. This answer solved my linking issues. Commented Nov 22, 2017 at 16:47
  • @afarnham I think it will do so for pretty much every library in the Swift "core" since it's attempting to link with them when linking in the stuff from the static library that's using Swift. I previously attempted to manually include every Swift library with the target dependencies and other build phases; needless to say it was a nightmare...and didn't work. I would hope Apple would make this a project setting so you don't have to have a dummy file in place to "trick" the primary target but this works for now I guess. Commented Nov 24, 2017 at 0:55
  • 1
    I just have a static library with a mix of objective-c and swift and i couldn't get the project (react-native) to compile :) Commented Jan 17, 2018 at 15:30
  • 2
    Amazing, just add a empty Swift file and all those errors go away. Thanks for the help! Commented Apr 10, 2018 at 18:10
  • 1
    I envy @thibautnoah. I have had this issue for several weeks now! Thanks a million! Commented Jun 4, 2018 at 10:03