Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SR-33] Support packaging Swift packages as dynamic libraries #5338

Closed
ahti opened this issue Dec 4, 2015 · 2 comments
Closed

[SR-33] Support packaging Swift packages as dynamic libraries #5338

ahti opened this issue Dec 4, 2015 · 2 comments
Assignees

Comments

@ahti
Copy link
Contributor

ahti commented Dec 4, 2015

Previous ID SR-33
Radar None
Original Reporter @ahti
Type New Feature
Status Closed
Resolution Done
Additional Detail from JIRA
Votes 6
Component/s Package Manager
Labels New Feature
Assignee @mxcl
Priority Medium

md5: c5e1c0ac4de9e353bcff819b4c922692

Issue Description:

From what I've read in the documentation about the package manager, it will currently statically link all code from dependencies into one final binary.

If (and hopefully when) Swift gains traction in the Linux community, Linux distributions will at some point in time want to integrate Swift packages into their native packaging mechanism. For this it would be advantageous to:

  1. have the ability to compile a Swift package into a dynamic library (maybe plus some more metadata) that can be packaged independently

  2. allow swift applications to be built to dynamically load their dependencies at runtime

The concept of dynamic frameworks on iOS/OSX could be used on Linux as well, having some sort of Swift packages/frameworks folder that packages will be sought for in when a binary is trying to load a dependency.

@mxcl
Copy link
Contributor

mxcl commented Dec 4, 2015

Yes, we agree.

@mxcl
Copy link
Contributor

mxcl commented Feb 17, 2016

This is implemented. See the SwiftPM Package.swift for an example.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 4, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants