Ive used an ebuild that installs a pre-compiled libffmpeg.so from Arch Linux,
/usr/local/portage/www-plugins/vivaldi-ffmpeg-codecs $ cat vivaldi-ffmpeg-codecs-54.0.2840.100.ebuild
Code: Select all
# Copyright 1999-2016 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Id$
EAPI=5
DESCRIPTION="Additional proprietary codecs for Vivaldi web browser, stable release."
HOMEPAGE="http://www.vivaldi.net"
SRC_URI="http://repo.herecura.eu/herecura/x86_64/${P}-1-x86_64.pkg.tar.xz"
LICENSE="LGPL2.1"
SLOT="0"
KEYWORDS="~amd64"
IUSE=""
DEPEND="www-client/vivaldi"
RDEPEND="${DEPEND}"
S=${WORKDIR}
src_unpack() {
unpack ${A}
}
src_install() {
cd ${S}
mkdir -p ${D}/opt/vivaldi/
cp ${S}/opt/vivaldi/libffmpeg.so ${D}/opt/vivaldi/libffmpeg.so
# mkdir -p ${D}/opt/vivaldi-snapshot/lib/
# rm ${D}/opt/vivaldi-snapshot/lib/libffmpeg.so
# ln -s ${D}/opt/vivaldi-snapshot/libffmpeg.so ${D}/opt/vivaldi-snapshot/lib/libffmpeg.so
}
Then theres a different ebuild for vivaldi-snapshot-ffmpeg-codecs but if I recall correctly, your installed version should be stable. The directory structure is different with stable and -snapshot version.
I am not 100 % sure, but if you compile chromium with system-ffmpeg flag, it might not create libffmpeg.so. Just my thought, but Im not sure about this.