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-674] swiftpm should expose a way to set rpath #5428

Open
swift-ci opened this issue Feb 4, 2016 · 3 comments
Open

[SR-674] swiftpm should expose a way to set rpath #5428

swift-ci opened this issue Feb 4, 2016 · 3 comments

Comments

@swift-ci
Copy link
Contributor

swift-ci commented Feb 4, 2016

Previous ID SR-674
Radar rdar://problem/27119493
Original Reporter jaybuff (JIRA User)
Type New Feature
Additional Detail from JIRA
Votes 0
Component/s Package Manager
Labels New Feature
Assignee None
Priority Medium

md5: 186d94abaf1ebb6e2c49fa8298c993b1

is duplicated by:

  • SR-1968 [SwiftPM] Need support for managing RPATH entries w.r.t. distribution
  • SR-6091 Module linked multiple times if dylib is importing same module that main executable does

relates to:

  • SR-1968 [SwiftPM] Need support for managing RPATH entries w.r.t. distribution

Issue Description:

There looks to be an undocumented way (e.g. setting SWIFTPM_EMBED_RPATH env var), but I take it that is only used for bootstrapping swift-build.

I'd prefer to be able to specify rpath in my Package.swift file.

@mxcl
Copy link
Contributor

mxcl commented Feb 17, 2016

The new Product component in Package.swift is perfect for this.

@mxcl
Copy link
Contributor

mxcl commented Mar 15, 2016

Also you can do this now:

swift build -Xlinker -rpath -Xlinker PATH

@abertelrud
Copy link
Contributor

It should be possible to control this other than needing to have custom flags passed on the command line to swift build every time. I'll take a look at what Product provides.

@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
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

4 participants