You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
have the ability to compile a Swift package into a dynamic library (maybe plus some more metadata) that can be packaged independently
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.
The text was updated successfully, but these errors were encountered:
Additional Detail from JIRA
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:
have the ability to compile a Swift package into a dynamic library (maybe plus some more metadata) that can be packaged independently
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.
The text was updated successfully, but these errors were encountered: