docummenting of usage dynamic_library_name

hello could you write in the docummentation or give me example how to use method dynamic_library_name to be able to include libloading after generating wrapper?

Input C/C++ Header

// Insert your minimal C or C++ header here.
//
// It should *NOT* have any `#include`s! Not all systems have the same header
// files, and therefore any `#include` harms reproducibility. Additionally,
// the test case isn't minimal since the included file almost assuredly
// contains things that aren't necessary to reproduce the bug, and makes
// tracking it down much more difficult.
//
// Use the `--dump-preprocessed-input` flag or the
// `bindgen::Builder::dump_preprocessed_input` method to make your test case
// standalone and without `#include`s, and then use C-Reduce to minimize it:
// https://github.com/rust-lang/rust-bindgen/blob/master/CONTRIBUTING.md#using-creduce-to-minimize-test-cases

Bindgen Invocation

bindgen::Builder::default()
    .header("input.h")
    .generate()
    .unwrap()

or

$ bindgen input.h --whatever --flags

Actual Results

Insert panic message and backtrace (set the `RUST_BACKTRACE=1` env var) here.

and/or

// Insert the (incorrect/buggy) generated bindings here

and/or

Insert compilation errors generated when compiling the bindings with rustc here

Expected Results

Search the bindgen documentation and API references for dynamic_library_name and review how generated wrappers are intended to work with libloading. Add a concise usage example showing the method in that workflow, then verify that the example accurately reflects the public API and explains the expected generated result.