Mercurial > crates > nonstick
diff libpam-sys/build.rs @ 190:995aca290452
Restructure the way libpam-sys-impls works to fix cross-compilation.
The previous structure of libpam-sys-impls meant that things got
confusing (including for me) between what constants were build-time
and what constants were run-time. This broke cross-compilation.
This simplifies the way that works so that `libpam-sys-impls` has
*no* build script itself and is intended mostly as a library to be
included in other libraries' build scripts (while also exporting
the PamImpl enum).
| author | Paul Fisher <paul@pfish.zone> |
|---|---|
| date | Sat, 02 Aug 2025 18:47:46 -0400 |
| parents | 0730f5f2ee2a |
| children | e915c54097d6 |
line wrap: on
line diff
--- a/libpam-sys/build.rs Thu Jul 31 15:42:12 2025 -0400 +++ b/libpam-sys/build.rs Sat Aug 02 18:47:46 2025 -0400 @@ -1,4 +1,26 @@ +use std::{env, fs}; + fn main() { println!("cargo:rustc-link-lib=pam"); libpam_sys_impls::enable_pam_impl_cfg(); + + let pam_impl = libpam_sys_impls::build_target_impl(); + let impl_str = pam_impl.map(|i| format!("{i:?}")).unwrap_or("[undefined]".into()); + println!("cargo:rustc-env=LIBPAMSYS_IMPL={impl_str}"); + let output = match pam_impl { + None => "".into(), + Some(pam_impl) => { + format!("\ + /// The implementation of PAM this library was built against. + pub const CURRENT: PamImpl = PamImpl::{pam_impl:?}; + /// The name of the PAM implementation this library was built + /// against, as a string. + #[macro_export] + macro_rules! pam_impl_name {{ () => {{ \"{pam_impl:?}\" }} }} + pub(crate) use pam_impl_name; + ") + } + }; + let outfile = format!("{out}/pam_impl_consts.rs", out = env::var("OUT_DIR").expect("missing OUT_DIR env var")); + fs::write(outfile, output).expect("couldn't write output file"); }