# How can I include my dependent framework's objects to my framework

**URL:** <https://forums.swift.org/t/how-can-i-include-my-dependent-frameworks-objects-to-my-framework/20455>\
**Category:** Using Swift\
**Tags:** swift, module, dependency\
**Created:** [February 13, 2019, 8:46pm UTC](https://forums.swift.org/t/how-can-i-include-my-dependent-frameworks-objects-to-my-framework/20455 "2019-02-13T20:46:59Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![SDGGiesbrecht](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/sdggiesbrecht/32/4768_2.png) [@SDGGiesbrecht](https://forums.swift.org/u/SDGGiesbrecht)\
**Post date:** [February 13, 2019, 9:02pm UTC](https://forums.swift.org/t/how-can-i-include-my-dependent-frameworks-objects-to-my-framework/20455/2 "2019-02-13T21:02:34Z")

</div>

There is no officially supported solution yet, but there is an incomplete, unofficial one which is already sufficient for most cases:

```swift
@_exported import BFramework

```

You can read about the remaining issues in this thread:

> [@@\_exported and fixing import visibility](https://forums.swift.org/t/exported-and-fixing-import-visibility/9415):
>
> I told @Jon_Shier I'd write something up on @\_exported and visibility in general, so here it is. It's a bit of a brain dump, but I know if I wait until I have time to edit it it won't get posted for months. (That's already true, in fact; I've had this model kicking around my head for probably close to a year now.) So, thanks for the prompt, Jon. Today, if your Swift library "Foo" uses a library "Bar", the headers (or swiftmodule files) of "Bar" must be available to all clients of "Foo". This i…

---

_[View the full topic](https://forums.swift.org/t/how-can-i-include-my-dependent-frameworks-objects-to-my-framework/20455)._