Skip to content
This repository was archived by the owner on Nov 18, 2022. It is now read-only.
This repository was archived by the owner on Nov 18, 2022. It is now read-only.

No way to specify custom target specifications relative to project #501

Open
@joepie91

Description

@joepie91

Since rls.toml was deprecated, the only way to specify a custom target in rls-vscode seems to be to configure the rust.target option in the workspace-specific configuration; unfortunately, it seems that relative paths are not supported here, or at least not seen as relative to the project (possibly related to #448?).

As it stands, it seems to only accept 1) rustc-provided target triples, and 2) absolute paths to custom target specifications. The former is obviously not an option for custom target specifications, and the latter isn't very portable; absolute paths are system-specific, so it would be essentially impossible to collaborate on a project with multiple people.

Perhaps this could be fixed in a similar manner to #448, by treating relative target paths as being relative to the project directory?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugenhancementIndicates new feature requestsrlsIssue related to the RLS itself rather than the extension

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions