# How to use a custom build configuration in a Swift Package?

**URL:** <https://forums.swift.org/t/how-to-use-a-custom-build-configuration-in-a-swift-package/36259>\
**Category:** Using Swift\
**Tags:** packagemanager\
**Created:** [May 7, 2020, 7:11pm UTC](https://forums.swift.org/t/how-to-use-a-custom-build-configuration-in-a-swift-package/36259 "2020-05-07T19:11:33Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![NeoNacho](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/neonacho/32/1368_2.png) [@NeoNacho](https://forums.swift.org/u/NeoNacho)\
**Post date:** [May 7, 2020, 8:05pm UTC](https://forums.swift.org/t/how-to-use-a-custom-build-configuration-in-a-swift-package/36259/6 "2020-05-07T20:05:42Z")

</div>

This seems more like a workaround than a solution to me, because now clients of that package need to use "MyConfigName" to get that behaviour. What if I am using two packages with different custom configurations that I need to use? I think this really only works if the packages and the client are tightly coupled, e.g. when you are using packages to break up a larger app.

What would be better is something like "Package Features" idea that Daniel mentioned in [My SwiftPM wishlist (aka proposal proposals)](https://forums.swift.org/t/my-swiftpm-wishlist-aka-proposal-proposals/35292), a way to opt in to building the package with additional build settings that is independent of the build configuration and can be selected on a per-package basis.

---

_[View the full topic](https://forums.swift.org/t/how-to-use-a-custom-build-configuration-in-a-swift-package/36259)._