Skip to content

Tracking Issue for native link modifier verbatim #99425

Closed

Description

@petrochenkov

This is a tracking issue for native link modifier verbatim, which is a part of RFC "Linking modifiers for native libraries" (#81490, rust-lang/rfcs#2951).
The feature gate for the issue is #![feature(native_link_modifiers_verbatim)].

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

Steps

Unresolved Questions

-l:libfoo.a is not entirely verbatim, there's still no way to pass a library by full path (without the -l option), like /path/to/libfoo.a, while still respecting relative order of passed libraries, -C link-arg=/path/to/libfoo.a will put the option at the end of the command line instead.
-l link-arg=/path/to/libfoo.a (#99427) will likely help with this situation.

Implementation history

Activity

  1. added
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    A-linkageArea: linking into static, shared libraries and binaries
    T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
    on Jul 18, 2022
  2. petrochenkov commented on Aug 6, 2022

    @petrochenkov
    ContributorAuthor

    Known issue: fn find_library in the compiler still falls back from "{target_staticlib_prefix}{name}{target_staticlib_suffix}"/"{name}" to "lib{name}.a" even if +verbatim is enabled, it shouldn't do that.

    Update: this was fixed in #101806.

  3. dpaoliello commented on Nov 9, 2022

    @dpaoliello
    Contributor

    Is there anything currently blocking the stabilization of this feature?

  4. petrochenkov commented on Nov 10, 2022

    @petrochenkov
    ContributorAuthor

    I think it can be stabilized now, if the limitations and the caveat about full paths are well documented.
    I can prepare the stabilization PR.

  5. petrochenkov commented on Nov 13, 2022

    @petrochenkov
    ContributorAuthor

    Stabilization PR - #104360.

  6. added a commit that references this issue on Nov 28, 2022
  7. added a commit that references this issue on Nov 28, 2023
  8. added a commit that references this issue on Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-linkageArea: linking into static, shared libraries and binariesC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions