Hi , i have an error building vlc from slackbuilds , i get error reference to libaom , if edit slackbuild and disable explicitly

then vlc , builds fine ...

other option , i see in archlinux use this version of libaom
https://aomedia.googlesource.com/aom...v1.0.0-errata1

I build that libaom , and then vlc , builds fine with libaom ...

I write this cause libaom , is a variable option autodetected , if some one have actually libaom from SBo
then you need disable it on slackbuild vlc , or go to build the libaom errata version.

Im not write the mantainer , cause im tired , ... some times no receive nothing, or write to say ..im not mantain ..get if you want ...or something similar...last time with pyrit , is not working well ,cause scapy changes , and need last git of pyrit , but say no mantain ,..nothing to do.

I hope writing here , some one , do something cause vlc, its more popular than pyrit.

Save yourself the heartache and just download AlienBob's VLC from his repository.

Enjoy!

1 members found this post helpful.

aom is garbage. ffmpeg has issues with it as well. I think that the only thing that it plays nice with is gst-plugins-bad.

My recommendation, avoid aom if you can.

The version of libaom available on SBo (which I maintain) is actually a recent git snapshot and sounds like it is unsuitable for the release version of vlc. Certainly my own experience with this script is to use it with the git FFmpeg and to use the 2 command line utilities that are built, as I mention in the readme:

In this case it works fine and I confess that I don't actually compile vlc on my system. Perhaps in the interest of a more integrated SBo experience somebody could take the script from me and build the release version instead?

I would recommend you have a look at FFmpeg + rav1e which is currently producing some pretty good results with AV1 encoding. I have done some work with this on my other Linux distro and I seriously think that it is the codec of the future.

libaom / aom is simply the reference encoder / decoder so it will probably never be a shining example but rav1e is definitely currently blazing the trail...

Of course, that is understood. If it's far more efficient and less tiresome to post to a forum rather than send an email, then why should someone of your expertise and importance need to follow the well known procedures that ordinary people are encouraged to follow?

In the next round of SBO updates, the SlackBuild for vlc will have an option to ignore an incompatible libaom by setting the environment variable LIBAOM=no during the building of vlc.

chris

2 members found this post helpful.

As i say , im tired to receive NOTHING , or "mantain you" ... thanks for option under vlc , i see in git change...probably in the next vlc release , libaom return to be compatible.

You know ,some script no mantained since years , im not understand why are you surprised...i see rworkman assume mantain of a big numbers of scripts , this last week.

Im write here cause in this case , can do more than one action , under vlc, or under libaom ... personally i build ffmpeg with libaom , and im disabling under vlc , i think if vlc use system ffmpeg probably no problems cause system ffmpeg are with aom support.

only binary packages i install are slackware oficial packages, ... all extra i build ever from source , and when you try to builds ...alienbob or alienpeter or alienfrank ... error is same for all if libaom are present.

I test building libaom same version like archlinux ,all works fine ...the other option is build vlc, without libaom , and as a last , install binary packages from some personal repository ... with the extra dependencies ... good luck , when you go install some from slackbuilds , and take conflicts with some library arrived from 3rth party binary repo....mixing packages from different repos are bad idea.

My own plan with the libaom SlackBuild was to allow Slackware users to be 'early adopters' in the AV1 world. For that purpose I have since August 2018 hosted regularly updated git snapshots on my own web site as there is currently no other good technique to get an 'official', up to date, tarball.

The second part of this plan is to wait for a more meaningful official 'release' from the aom developers than the current various 'errata' releases. aom is still very much coming of age so things are currently in a bit of flux to say the least.

Once stage 2 of my plan is in place I suspect that things will settle down a little with regards to vlc, FFmpeg and friends and then hopefully there will be a little less angst from end users

I always use alienbob VLC and qt5 and some other stuff he builds, it saves a lot of time. other stuff yes I use slackbuilds. I'd say go use alienbob VLC save your self head aches

1 members found this post helpful.

After the next SBo update, which I believe should be in a day or so, 'libaom' should vanish and 'aom' 2.0.0 should appear. Finally this is a solid, long lasting, release of aom with no more self-hosted git snapshots and hopefully vlc, FFmpeg and other friends will catch up soon enough...

I build vlc , with aom-2


--enable-aom

works perfectly now.

The libaom package version 1 , goes to removed in the next update slackbuilds cycle.

https://git.slackbuilds.org/slackbui...b6f6796cd8effe

1 members found this post helpful.

Just for completeness regarding support for AV1, vlc also recognizes and uses SBo's libraries/dav1d for this purpose.

chris

i build with dav1d too ...


and other extra packages all from SBo ... i build using qt5 , and all works perfectly , im not test if qt4 problems goes fixed under vlc-3.0.10

Good work.

I don't think you need to explicitly --enable-{aom,dav1d}. Here they are automatically detected by vlc's configure script.

chris