Skip to content
This repository has been 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 opened this issue Feb 10, 2019 · 1 comment
Open
Labels
bug enhancement Indicates new feature requests rls Issue related to the RLS itself rather than the extension

Comments

@joepie91
Copy link

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?

@Xanewok
Copy link
Member

Xanewok commented Apr 7, 2019

#448 is solved now, could you see if the relative paths work now?

@Xanewok Xanewok added bug enhancement Indicates new feature requests rls Issue related to the RLS itself rather than the extension labels Apr 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug enhancement Indicates new feature requests rls Issue related to the RLS itself rather than the extension
Projects
None yet
Development

No branches or pull requests

2 participants