rust/tests/ui/link-native-libs/suggest-libname-only-2.rs

//@ build-fail
//@ compile-flags: --crate-type rlib

#[link(name = "bar.lib", kind = "static")]
extern { } //~ WARN `extern` declarations without an explicit ABI are deprecated
           //~| HELP explicitly specify the "C" ABI

pub fn main() { }

//~? ERROR could not find native static library `bar.lib`
//~? HELP only provide the library name `bar`, not the full filename
Add suggestion to the "missing native library" error If we fail to locate a native library that we are linking with, it could be the case the user entered a complete file name like `foo.lib` or `libfoo.a` when we expect them to simply provide `foo`. In this situation, we now detect that case and suggest the user only provide the library name itself. 2022-10-12 22:52:31 -04:00			`//@ build-fail`
			`//@ compile-flags: --crate-type rlib`

			`#[link(name = "bar.lib", kind = "static")]`
Add test for `extern` without explicit ABI 2025-04-08 05:31:24 +03:00			extern { } //~ WARN `extern` declarations without an explicit ABI are deprecated
UI tests: migrate remaining compile time `error-pattern`s to line annotations when possible. 2025-04-12 22:40:34 +03:00			`//~\| HELP explicitly specify the "C" ABI`
Add suggestion to the "missing native library" error If we fail to locate a native library that we are linking with, it could be the case the user entered a complete file name like `foo.lib` or `libfoo.a` when we expect them to simply provide `foo`. In this situation, we now detect that case and suggest the user only provide the library name itself. 2022-10-12 22:52:31 -04:00
			`pub fn main() { }`
compiletest: Require `//~` annotations even if `error-pattern` is specified 2025-03-29 02:41:32 +03:00
			//~? ERROR could not find native static library `bar.lib`
UI tests: migrate remaining compile time `error-pattern`s to line annotations when possible. 2025-04-12 22:40:34 +03:00			//~? HELP only provide the library name `bar`, not the full filename