# What is the risk of having dependencies in my framework with BUILD\_LIBRARIES\_FOR\_DISTRIBUTION as false?

**URL:** <https://forums.swift.org/t/what-is-the-risk-of-having-dependencies-in-my-framework-with-build-libraries-for-distribution-as-false/48126>\
**Category:** Using Swift\
**Created:** [May 11, 2021, 7:01am UTC](https://forums.swift.org/t/what-is-the-risk-of-having-dependencies-in-my-framework-with-build-libraries-for-distribution-as-false/48126 "2021-05-11T07:01:35Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![nominalista](https://avatars.discourse-cdn.com/v4/letter/n/e56c9b/32.png) [@nominalista](https://forums.swift.org/u/nominalista)\
**Post date:** [May 11, 2021, 10:11am UTC](https://forums.swift.org/t/what-is-the-risk-of-having-dependencies-in-my-framework-with-build-libraries-for-distribution-as-false/48126/3 "2021-05-11T10:11:58Z")

</div>

Thank you for a quick response! Sounds very reassuring.

Would like to mention, that I planned to use CocoaPods for the distribution. I've noticed that, if my framework has dependencies specified in a `.podspec` file, then all the dependencies are explicitly added to the client's app during `pod install` phase. Even if I'm using `@_implementationOnly` import. Is it because CocoaPods adds dependencies dynamically instead of linking them statically like SPM? Should I be worried if these dependencies can't be built with the `BUILD_LIBRARIES_FOR_DISTRIBUTION` flag?

I'm not sure whether SPM will be an option for me, but how it works internally, I mean will the dependencies of the framework be build with the `BUILD_LIBRARIES_FOR_DISTRIBUTION` flag or it's not happening when they're statically linked to the framework?

---

_[View the full topic](https://forums.swift.org/t/what-is-the-risk-of-having-dependencies-in-my-framework-with-build-libraries-for-distribution-as-false/48126)._