Package: opusfile-devel (0.12-bp160.1.14)
Development package for opusfile
Files for development with opusfile.
Package information
- Homepage
- [https://www.opus-codec.org/]
- License
- BSD-3-Clause
- Downstream package maintainer
- Unknown: not reported in the indexed source
- Source package
- [opusfile]
- Software project
- [opusfile]
Versions and downloads for opusfile-devel
| Version / release | Architecture / repository | Package size | Installed size | Files | Publisher repository artifact |
|---|---|---|---|---|---|
| 0.12-bp160.1.14leap-16.0 / oss | aarch64openSUSE Leap 16.0 · OSS · multi-architecture | 34 KiB | 117 KiB | list of files | opusfile-devel-0.12-bp160.1.14.aarch64.rpm |
| 0.12-bp160.1.14leap-16.0 / oss | ppc64leopenSUSE Leap 16.0 · OSS · multi-architecture | 34 KiB | 117 KiB | list of files | opusfile-devel-0.12-bp160.1.14.ppc64le.rpm |
| 0.12-bp160.1.14leap-16.0 / oss | s390xopenSUSE Leap 16.0 · OSS · multi-architecture | 34 KiB | 117 KiB | list of files | opusfile-devel-0.12-bp160.1.14.s390x.rpm |
| 0.12-bp160.1.14leap-16.0 / oss | x86_64openSUSE Leap 16.0 · OSS · multi-architecture | 34 KiB | 117 KiB | list of files | opusfile-devel-0.12-bp160.1.14.x86_64.rpm |
About these downloads
Each row is recorded package-index metadata for one version, architecture, suite, and repository. Names, URLs, and sizes are source-reported; a link is a potentially mutable retrieval location, not an OpenFactory redistribution claim or proof that OpenFactory retained the artifact bytes.
Other packages built from opusfile
- libopusfile0
A high-level API for decoding and seeking within .opus files
Dependencies and recommendations for opusfile-devel
dep: /usr/bin/pkg-config
Package not available
dep: [libopusfile0] (= 0.12)
A high-level API for decoding and seeking within .opus files
dep: pkgconfig
Package not available
dep: pkgconfig(ogg) (>= 1.3)
Package not available
dep: pkgconfig(openssl)
Package not available
dep: pkgconfig(opus) (>= 1.0.1)
Package not available
dep: pkgconfig(opusfile)
Package not available
Package file paths (9)
Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.
- /usr/include/opus/opusfile.h
- /usr/lib64/libopusfile.so
- /usr/lib64/libopusurl.so
- /usr/lib64/pkgconfig/opusfile.pc
- /usr/lib64/pkgconfig/opusurl.pc
- /usr/share/doc/opusfile
- /usr/share/doc/opusfile/AUTHORS
- /usr/share/doc/opusfile/COPYING
- /usr/share/doc/opusfile/README.md
Field source: openSUSE Leap 16.0 OSS
