Skip to content

Consider adding the absolute CFG_LIBDIR to the search paths for rustc #11068

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.

Sign up for GitHub

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

Jump to bottom
Closed
alexcrichton opened this issue Dec 19, 2013 · 2 comments
Closed

Consider adding the absolute CFG_LIBDIR to the search paths for rustc #11068

alexcrichton opened this issue Dec 19, 2013 · 2 comments

Comments

@alexcrichton
Copy link
Member

In #11045, we're probably going to start always having an absolute path for CFG_LIBDIR. This means that librustc has one extra location to start search for by default for the target libraries. This libdir is essentially the same thing as self_exe_path().pop() for rustc, but as #11063 noted other usage of librustc is hamstrung by having to specify this directory.
@alexcrichton alexcrichton mentioned this issue Dec 19, 2013
Closed
@alexcrichton alexcrichton mentioned this issue Jan 25, 2014
Closed
@steveklabnik
Copy link
Member

Triage: unclear what the status is of this today.

@alexcrichton
Copy link
Member Author

I think we've got our story pretty square here today, so closing.

flip1995 pushed a commit to flip1995/rust that referenced this issue Jul 14, 2023
@bors
Auto merge of rust-lang#11078 - Centri3:11068, r=llogiq
ba3bd8f 
[`needless_raw_string_hashes`]: Only reset hashes needed if not following quote

Fixes rust-lang#11068

changelog: none
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@steveklabnik @alexcrichton