Crates.io | oefpil-sys |
lib.rs | oefpil-sys |
version | |
source | src |
created_at | 2024-12-11 23:33:28.72244 |
updated_at | 2024-12-11 23:33:28.72244 |
description | Rust FFI bindings to statically linked C/Fortran library OEFPIL |
homepage | |
repository | https://github.com/qu1x/oefpil |
max_upload_size | |
id | 1480611 |
Cargo.toml error: | TOML parse error at line 28, column 1 | 28 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
Rust FFI bindings to statically linked C/Fortran library OEFPIL
For a safe API, see the oefpil
crate.
See the release history to keep track of the development.
By default, this crate dynamically links to the runtime dependency liblapack
(e.g., package
liblapack3
on Debian, package lapack
on Fedora Linux or Arch Linux) and requires a C
compiler as build dependency (e.g., package clang
or gcc
on Debian, Fedora Linux, or Arch
Linux). With the built-in
feature, a subset of liblapack
and its dependency libblas
shipped with this crate is compiled and statically linked. This eliminates the runtime
dependency liblapack
but requires the GCC Fortran compiler (e.g, gfortran
on Debian,
gcc-fortran
on Fedora Linux or Arch Linux) as build dependency which itself depends on and
complements the GCC C compiler such that GCC can compile both C and Fortran sources. It is
attempted to statically link the dependencies of the subset (i.e, libgfortran
and
libquadmath
) whereas dynamic linking serves as fallback if no static libraries are found.
This combined work is free, open source, open collaboration, and permissively licensed.
Except where noted (below and/or in individual files), this combined work is dual-licensed under
either MIT
or Apache-2.0
at your option. This means you can select the license you prefer.
This dual-licensing approach is the de-facto standard in the Rust ecosystem. For full authorship
information, see the individual files and/or the commit history.
The dependencies shipped with this combined work are licensed as follows:
MIT
.BSD-3-Clause
.Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the
work by you, as defined in the Apache-2.0
license, shall be dual-licensed as above, without any
additional terms or conditions.