| Git Clone URL: | https://aur.archlinux.org/lib32-ffmpeg.git (read-only, click to copy) |
|---|---|
| Package Base: | lib32-ffmpeg |
| Description: | Complete solution to record, convert and stream audio and video (32 bit) |
| Upstream URL: | http://ffmpeg.org |
| Licenses: | GPL-3.0-only |
| Conflicts: | lib32-libffmpeg |
| Provides: | libavcodec.so, libavdevice.so, libavfilter.so, libavformat.so, libavutil.so, libpostproc.so, libswresample.so, libswscale.so |
| Replaces: | lib32-libffmpeg |
| Submitter: | lano1106 |
| Maintainer: | oxalin |
| Last Packager: | oxalin |
| Votes: | 37 |
| Popularity: | 0.042020 |
| First Submitted: | 2013-05-18 04:43 (UTC) |
| Last Updated: | 2024-08-03 20:23 (UTC) |
Here we go. I'm using the vanilla x265.pc file
prefix=/usr
exec_prefix=${prefix}
libdir=${exec_prefix}/lib32
includedir=${prefix}/include
Name: x265
Description: H.265/HEVC video encoder
Version: 3.0
Libs: -L${libdir} -lx265
Libs.private: -lstdc++ -lm -lgcc_s -lgcc -lgcc_s -lgcc -lrt -ldl -lnuma
Cflags: -I${includedir}
@QuartzDragon : Nothing was changed from previous version (4.1.3) on that matter. However, some changes were made to a previous version.
Is lib32-x265 installed? If so, is it up to date? lib32-x265 was not correctly setting up its .pc file until recently (when I proposed a fix). Could you share your x265.pc file (/usr/lib32/pkgconfig/x265.pc)?
Anyone else getting this error, even with the latest lib32-x265 installed?
==> Starting build()...
ERROR: x265 not found using pkg-config
If you think configure made a mistake, make sure you are using the latest
version from Git. If the latest version fails, report the problem to the
ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net.
Include the log file "ffbuild/config.log" produced by configure as this will help
solve the problem.
==> ERROR: A failure occurred in build().
Aborting...
@QuartzDragon: no, I don't have any problem when rebuilding from scratch. Thanks for the cue about lib32-aom. I'm pushing an updated package right now.
Also, you can enable lib32-aom now, as it exists. :)
Does anyone else's build just hang forever trying to link:
LD libswresample/libswresample.so.3
@mokkurkalve indeed, it still fails. lib32-x264 should be fixed to address the problem: pkgver was not properly updated as it should have.
The maintainer of lib32-x264 yesterday DID what you asked in your comment over there, he updated to revision 72db437770fd1ce3961f624dd57a8e75ff65ae0b. But by then you had updated lib32-ffmpeg to demand v 157, which he DID NOT update for.... So lib32-ffmpeg can still not be installed, it just throws: ==> Error: Could not find all required packages: lib32-x264>=157 (Wanted by: lib32-ffmpeg)
@sl1pkn07 : you are right. I dropped it in 4.1.3.
Hi
ffmpeg from [extra] not include libavresample (marked as deprecated by upstream). this package should do the same?
greetings
Pinned Comments
oxalin commented on 2024-04-09 22:05 (UTC)
For those wondering: I intentionally keep this package as close to the native package as possible, to the extent of the available dependencies. FFMPEG package sees a lot of modifications through time and I prefer to follow the changes applied to the native PKGBUILD as much as possible. The more it goes, the more flags are added and the more often we need to cherrypick commits (until a new release comes in).
This means I'll keep the dependencies around even if there is no obvious usecase for them.
Also, since openjpeg2 is still used with the native package, I'll also keep it around. Last thing I read about the JPEG2000 internal decoder was that it was faster, but that it was still introducing errors in the rendering. This probably explains why it is still enable in the native package. I look at it once in a while and things may have evolved since, but a quick checkup didn't bring up any tangible answer.
Now, if someone would like to take the ownership of this package, I would be more than pleased to hand it over. The same goes for any related packages that I maintain mostly for FFMPEG. lib32-libffmpeg and lib32-ffmpeg could be merged back together to simplify its maintenance.
Let me know if this is something you're interested in.
oxalin commented on 2018-02-25 07:37 (UTC) (edited on 2020-05-25 15:55 (UTC) by oxalin)
About GPG, it is up to you to import the missing public key. If you receive an error about it, this is ffmpeg's project public key. Something like the following should do the trick: gpg --recv-keys B4322F04D67658D8