-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Clarify documentation regarding +bundle
linkage modifier
#112384
Conversation
(rustbot has picked a reviewer for you, use r? to override) |
r? compiler |
cc @fee1-dead |
I am not familiar with this. r? compiler |
Github for some reason, doesn't want to show this commit in PR: In-line@6431df9 |
+bundled
linkage modifier+bundle
linkage modifier
Co-authored-by: David Wood <[email protected]>
Things became a bit more complex after #111698. Unspecified kind can now mean either |
@@ -62,11 +62,15 @@ attribute or on the command-line, it will link a dynamic library if available, | |||
otherwise it will use a static library. If the kind is specified on the | |||
command-line, it will override the kind specified in a `link` attribute. | |||
|
|||
If you don't specify `KIND`, no linkage modifiers will be applied. | |||
For instance, [`+bundle` linkage modifier][bundle-modifier] won't be used in conjunction with static library by default. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Of course it won't be used, because there won't be any static library.
When this PR was submitted, unspecified kind always meant dylib
.
ping from triage - can you post your status on this PR? There hasn't been an update in a few months. Thanks! FYI: when a PR is ready for review, send a message containing |
Closing this as inactive. Feel free to reöpen this pr or create a new pr if you get the time to work on this. Thanks |
No description provided.