# Roadmap of SwiftPM Integration into Xcode

**URL:** <https://forums.swift.org/t/roadmap-of-swiftpm-integration-into-xcode/13466>\
**Category:** Package Manager\
**Tags:** spm, xcode\
**Created:** [June 9, 2018, 8:51am UTC](https://forums.swift.org/t/roadmap-of-swiftpm-integration-into-xcode/13466 "2018-06-09T08:51:50Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![fabb](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/fabb/32/2230_2.png) [@fabb](https://forums.swift.org/u/fabb)\
**Post date:** [June 30, 2018, 11:37am UTC](https://forums.swift.org/t/roadmap-of-swiftpm-integration-into-xcode/13466/18 "2018-06-30T11:37:16Z")

</div>

Maybe Carthage could be leveraged until SwiftPM can stand on its own feet?

[https://github.com/Carthage/Carthage/pull/1945](https://github.com/Carthage/Carthage/pull/1945)

Still there‘d be a gap of missing features in SwiftPM to make this the new de-facto standard. Top of mind would be build settings ([SR-3948](https://bugs.swift.org/browse/SR-3948); at least iOS deployment version) and packaging resources ([SR-2866](https://bugs.swift.org/browse/SR-2866)).

More nice-to-have features are mentioned in this thread: [Swift Package Manager Evolution Ideas](https://forums.swift.org/t/swift-package-manager-evolution-ideas/13940)

---

_[View the full topic](https://forums.swift.org/t/roadmap-of-swiftpm-integration-into-xcode/13466)._