Is it intended that the (library) build succeeds on non-macOS/iOS?

[eddyb]

ash-molten/build/build.rs

Lines 375 to 378 in 09bed93

	#[cfg(not(any(target_os = "macos", target_os = "ios")))]
	fn main() {
	eprintln!("ash-molten requires either 'macos' or 'ios' target");
	}

That build script will just print a message that will never be forwarded to the user, because it also "succeeds" (since it doesn't panic, nor exit with a non-0 return code - either via fn main() -> ... or std::process::exit).

Is this intentional? cargo run, and many other uses of the library, will still fail with a linker error.

[MarijnS95]

I suggested to do the same in #56 (comment), or even replace it with println!("cargo:rustc-link-lib=vulkan"); to be able to build-test this crate on non-Mac (even though that's trivial and part of core ash now).

[eddyb]

Heh, this "bug"(?) made testing my PR (#71) easier, and I could see the appeal.
We could maybe at least emit a cargo:warning= with a message like "this crate doesn't do anything outside of macOS/iOS".

Oh but Cargo isn't printing those for dependencies by default. Maybe the exported function could just panic at runtime?