All about linking libraries

on YouTube ↗07m

" summary

Explains how linking fails and how to fix it by showing the actual build settings and file layout that cause errors: when a dependency lacks modules use module maps or bridging headers, when a dependency is dynamic add a copy frameworks build phase, and when symbols disappear check header paths and search-path settings. Demonstrates concrete Xcode settings to change, the runtime difference between static and dynamic libraries, and simple troubleshooting steps that reproduce and then resolve missing-module and duplicate-symbol errors.

AI-written summary · about

" chapters (11)

1. 0:00Start
2. 0:29Dragging to Embedded Binaries
3. 0:52Dynamic vs Static wl Bundle vs wo/Bundle
4. 2:02What need to import libraries into Swift?
5. 2:50Set parent directory of the framework to Framework Search Paths
6. 3:20a. Bridging Header
7. 4:28How to import libraries
8. 4:38a Bridging Header
9. 5:15Link dynamic frameworks
10. 5:32How to link libraries
11. 6:17Recap

" related talks

• 25mUse C, C++ and Objective C Libraries in a Swift ProjectCecilia Humlelu · App Builders Switzerland 2019
• 58mMaking Libraries Consumable for Non-C++ DevelopersAaron R Robinson · CppCon 2021
• 01h 04mBuilding ModulesMichael Spencer · CppCon 2019
• 41mWe Don’t Talk About XcodeJames Dempsey · 360iDev 2022
• 01h 17mDevelopment strategies: You've written a library - now what?Marshall Clow · CppCon 2018
• 45mSwift, Frameworks & Modules, Learnings from CocoaPodsOrta Therox, Marius Rackwitz · GOTO Copenhagen 2015
• 43mLibrary Developer ConfidentialElliott Chenger · 360|AnDev 2018
• 47mBuilding and Integrating FrameworksSean Coleman · 360|iDev 2016