Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 5 Sep 2017 22:21:00 -0700
From:      Kevin Oberman <rkoberman@gmail.com>
To:        Andrew <andrewter@comcast.net>
Cc:        multimedia@freebsd.org
Subject:   Re: FreeBSD Port: multimedia/avidemux
Message-ID:  <CAN6yY1u9-TopHyifRfZRiqV4YEHWoWAAEd8fLF4347zTHHHbXQ@mail.gmail.com>
In-Reply-To: <d1ecd3e5-2bf5-3b55-5528-737acde2fc9c@comcast.net>
References:  <d1ecd3e5-2bf5-3b55-5528-737acde2fc9c@comcast.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Sep 5, 2017 at 9:41 PM, Andrew <andrewter@comcast.net> wrote:

> Hi,
>
> Are there any plans to update to the port to the latest upstream version
> 2.6.20?
>
> Thanks,
> Andrew
>

I have been working off and on on this and I THINK I am getting close, but
I m not a coder and was planning on opening a ticket since it is unstable
on  HEAD and 11 after the MFC of 320666 and  dumps core inconsistently when
resuming play. The problem appears to be with qt4, but it seems VERY
unlikely that qt4 will be fixed, so I decided to switch to using qt5 which
is supported upstream by avidemux.

Instead of just enabling qt5, I decided to look at moving to qt5 and
2.6.19. While I moved through several issues, 2.7 has been released, so I
am now moving to that one. My issue with 2.6.19 was with nasm in ffmpeg. It
did not configure with the BSD implementation of nasm.

Yesterday I discovered that 2.7 is out and has moved to ffmpeg 3.3. I am
hopeful that I can get a bit further... at least dealing with the nasm
issue as I can crib off the multimedia/ffmpeg port. Still, I am not a
coder, have VERY little C++ and no cmake experience, so any assistance
would be appreciated.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1u9-TopHyifRfZRiqV4YEHWoWAAEd8fLF4347zTHHHbXQ>