rust/tests/ui/manual/manual-link-bad-kind.rs

// compile-flags:-l bar=foo
// error-pattern: unknown library kind `bar`, expected one of: static, dylib, framework, link-arg

fn main() {
}
rustc: Remove support for `-l foo:static` This syntax has been renamed to `-l static=foo` some time ago. 2015-03-26 23:34:05 +00:00			`// compile-flags:-l bar=foo`
Lib kind -l link-arg: arbitrary link argument like -C link-arg, but respecting relative order to other `-l` options, unstable 2022-07-19 09:00:28 +00:00			// error-pattern: unknown library kind `bar`, expected one of: static, dylib, framework, link-arg
rustc: Implement -l and include! tweaks This is an implementation of the rustc bits of [RFC 403][rfc]. This adds a new flag to the compiler, `-l`, as well as tweaking the `include!` macro (and related source-centric macros). The compiler's new `-l` flag is used to link libraries in from the command line. This flag stacks with `#[link]` directives already found in the program. The purpose of this flag, also stated in the RFC, is to ease linking against native libraries which have wildly different requirements across platforms and even within distributions of one platform. This flag accepts a string of the form `NAME[:KIND]` where `KIND` is optional or one of dylib, static, or framework. This is roughly equivalent to if the equivalent `#[link]` directive were just written in the program. The `include!` macro has been modified to recursively expand macros to allow usage of `concat!` as an argument, for example. The use case spelled out in RFC 403 was for `env!` to be used as well to include compile-time generated files. The macro also received a bit of tweaking to allow it to expand to either an expression or a series of items, depending on what context it's used in. [rfc]: https://github.com/rust-lang/rfcs/pull/403 2014-10-21 06:04:16 +00:00
			`fn main() {`
			`}`