libmount-sys 0.1.1

Unsafe Rust bindings for libmount of util-linux
Documentation
  • Coverage
  • 0.22%
    1 out of 447 items documented0 out of 12 items with examples
  • Size
  • Source code size: 34.41 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 6.13 MB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 45s Average build duration of successful builds.
  • all releases: 45s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • wtm/libmount-sys
    0 0 1
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • micromaomao

crates.io docs.rs

libmount-sys: Unsafe Rust bindings for libmount of util-linux

The libmount library is used to, among other things:

  • Parse /etc/fstab, /etc/mtab and /proc/self/mountinfo files,
  • Manage the mtab file,
  • Evaluate mount options.

This crate is Linux-specific. Building it for non-Linux platforms, or for the Linux kernel, results in an empty crate.

This crate links to libmount, and requires it to be installed. See below for example installation instructions.

Installing libmount

This crate links to libmount, and requires it to be installed.

The library, its C header files, and the clang compiler need to be installed on the build machine. On Debian, for example, one can install that as follows:

sudo apt install clang libmount-dev

If the library is linked dynamically (most typical configuration), then it needs to be installed on the target computer in order to run the resulting program. On Debian, for example, one can install it as follows:

sudo apt install libmount1

Supported environment variables

This crate depends on some environment variables, and variants of those. For each environment variable (e.g., CC), the following are the accepted variants of it:

  • <var>_<target>, e.g., CC_aarch64-unknown-linux-gnu.
  • <var>_<target-with-underscores>, e.g., CC_aarch64_unknown_linux_gnu.
  • TARGET_<var>, e.g., TARGET_CC.
  • <var>, e.g., CC.

The following environment variables (and their variants) affect how this crate is built:

  • LIBMOUNT_STATIC
  • LIBMOUNT_PATH
  • LIBMOUNT_INCLUDE_DIR
  • LIBMOUNT_LIB_DIR
  • SYSROOT
  • CC
  • CFLAGS

Dynamic or static linking

This crate links to libmount dynamically if possible, except when targeting platforms based on the musl C library.

This behavior can be changed either by setting the environment variable LIBMOUNT_STATIC to 1, or by enabling the crate feature static. If both are defined, then the value of LIBMOUNT_STATIC takes precedence.

Setting LIBMOUNT_STATIC to 0 mandates dynamic linking.

Finding libmount library and headers

By default, this crate finds libmount headers and library based on the default target C compiler.

This behavior can be changed by:

  • Either defining the environment variable LIBMOUNT_PATH to the path of a directory containing the subdirectories include and lib where the headers and library are installed.
  • Or by defining one or both of the environment variables LIBMOUNT_INCLUDE_DIR and LIBMOUNT_LIB_DIR to paths to the directories where headers and library are present. If LIBMOUNT_PATH is also defined, then LIBMOUNT_INCLUDE_DIR and LIBMOUNT_LIB_DIR take precedence.

Depending on this crate

This crate provides the following variables to other crates that depend on it:

  • DEP_LIBMOUNT_INCLUDE: Path of the directory where library C header files reside.
  • DEP_LIBMOUNT_LIB: Path of the directory where the library binary resides.

Versioning

This project adheres to Semantic Versioning. The CHANGELOG.md file details notable changes over time.