rust/tests/ui-fulldeps/macro-crate-rlib.rs

// aux-build:rlib-crate-test.rs
// ignore-cross-compile gives a different error message

#![feature(plugin)]
#![plugin(rlib_crate_test)]
//~^ ERROR: plugin `rlib_crate_test` only found in rlib format, but must be available in dylib

fn main() {}
Moved issue tests to subdirs and normalised names. 2019-03-12 00:49:17 +00:00			`// aux-build:rlib-crate-test.rs`
test: Try to fix a failing snapshot test This test seems to yield a different error message on cross compiles, so just ignore it when cross compiling. 2014-07-15 14:00:37 -07:00			`// ignore-cross-compile gives a different error message`
rustc: Forbid plugin_registrar in only rlib form If a plugin registrar is available, the library must be found in dylib form, not just in rlib form. Closes #15475 2014-07-09 19:13:28 -07:00
Replace #[phase] with #[plugin] / #[macro_use] / #[no_link] 2014-12-31 20:43:46 -08:00			`#![feature(plugin)]`
Use a crate attribute to load plugins #[plugin] #[no_link] extern crate bleh; becomes a crate attribute #![plugin(bleh)] The feature gate is still required. It's almost never correct to link a plugin into the resulting library / executable, because it will bring all of libsyntax and librustc with it. However if you really want this behavior, you can get it with a separate `extern crate` item in addition to the `plugin` attribute. Fixes #21043. Fixes #20769. [breaking-change] 2015-02-06 13:56:38 -08:00			`#![plugin(rlib_crate_test)]`
rustc_metadata: Make crate loading fully speculative 2020-07-05 10:39:15 +03:00			//~^ ERROR: plugin `rlib_crate_test` only found in rlib format, but must be available in dylib
rustc: Forbid plugin_registrar in only rlib form If a plugin registrar is available, the library must be found in dylib form, not just in rlib form. Closes #15475 2014-07-09 19:13:28 -07:00
			`fn main() {}`