Crates.io | libcec-sys |
lib.rs | libcec-sys |
version | |
source | src |
created_at | 2019-10-30 19:33:11.788182 |
updated_at | 2024-12-22 12:44:02.57038 |
description | FFI bindings to libcec |
homepage | https://github.com/ssalonen/libcec-sys |
repository | https://github.com/ssalonen/libcec-sys |
max_upload_size | |
id | 177010 |
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 |
FFI bindings for the libcec
This crate works with libcec
v4.x, v5.x and v6.x (latest version as time of writing). During the build we try to find libcec
system library installation using pkg-config
and compilation using default C compiler (cc
crate).
As a fallback, static pre-built libcec
(v6.0.2) is downloaded from ssalonen/libcec-static-builds. Most common targets are supported.
There are vendored
and static
feature to allow more explicit control. There are also LIBCEC_VENDORED
and LIBCEC_STATIC
environment variables, just set them to value 1
.
The crate is tested mainly with Linux and Windows but could work with other platforms as well. PRs welcome.
On Linux, for most convenient build process, it is recommended to install pkg-config
, libcec-dev
(headers and pkg-config configuration), libcec6
(dynamic library), libp8-platform-dev
and libp8-platform2
from your package distribution before installing this crate. Exact package names vary between distributions and package managers.
In addition libudev-dev
might be needed.
With debian based distributions, you can simply
sudo apt-get install libudev-dev libp8-platform2 libp8-platform-dev libcec-dev pkg-config libcec6
If your environment lacks the needed dependencies, most easy option might be to fallback to static
build.
NOTE: new versions of Raspberry Pi OS should support standard linux API for CEC control. Static builds used by this library have the linux API enabled.
On Windows, probably easiest is to let the libcec-sys
fallback to statically pre-built library. One can request this explicitly by using LIBCEC_STATIC=1
environment variable or by using static
feature.
For dynamic linking: On Windows, it is recommended to install libcec
via the installer and add cec.dll
to the PATH
environment variable.
For a vendored build: libcec-sys
will dynamically link to the compiled cec.dll
. This means you must package your standalone executable with the compiled dynamic library.
Desktop Development with C++
and Universal Windows Platform development
Static build has been adapted from great work from @opeik in https://github.com/ssalonen/cec-rs/issues/52
See https://github.com/ssalonen/libcec-static-builds
This repo contains content distributed under three different licenses.
Main package, licensed under GNU General Public License version 2, (LICENSE or https://opensource.org/licenses/GPL-2.0)
The CI/CD setup in .github/
is based on rust-github/template, and therefore licensed under either of
at your option.
The CI uses sccache build cache tooling as shared in Cross repository wiki. The Cross repo itself is licensed under either of
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.
See CONTRIBUTING.md.
cargo release --no-publish --dev-version --execute
and let the github CD pipeline do the rest.