view src/libpam/mod.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 46e8ce5cd5d1
children
line wrap: on
line source

//! The implementation of the PAM interface that wraps `libpam`.
//!
//! While you're going to want to write PAM modules and applications against
//! the interfaces in [the `handle` module](crate::handle) for testability,
//! this is (probably) what will be used behind the scenes.

#![allow(dead_code)]

mod answer;
mod conversation;
mod environ;
mod handle;
mod items;
mod memory;
#[doc(hidden)]
pub mod module;
mod question;

#[doc(inline)]
pub use handle::{LibPamHandle, LibPamTransaction, TransactionBuilder};