# Ship static library as binary dependency in Package Manager

**URL:** <https://forums.swift.org/t/ship-static-library-as-binary-dependency-in-package-manager/42308>\
**Category:** Using Swift\
**Tags:** xcode, dynamic, packagemanager, static, ios\
**Created:** [November 27, 2020, 10:03am UTC](https://forums.swift.org/t/ship-static-library-as-binary-dependency-in-package-manager/42308 "2020-11-27T10:03:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![GLinnik21](https://avatars.discourse-cdn.com/v4/letter/g/87869e/32.png) [@GLinnik21](https://forums.swift.org/u/GLinnik21)\
**Post date:** [November 27, 2020, 10:03am UTC](https://forums.swift.org/t/ship-static-library-as-binary-dependency-in-package-manager/42308/1 "2020-11-27T10:03:50Z")

</div>

Hello everyone!  
I develop a close-sourced library that used to be shipped with CocoaPods in two variants: static and dynamic. Now the time has come to adopt SPM and I wonder if I can ship it as a static library? I found some difficulties with it because there is no out-of-the-box solution.

1. Static library needs other libraries it depends on to properly link
2. Even though I can bypass the 1-st problem, Xcode embeds static library inside [App].app/Frameworks, that is pointless.

So does SPM even designed to ship static libraries as binary dependencies?
