[mythtv] FFmpeg 4.4.1 problems
Peter Bennett
pb.mythtv at gmail.com
Thu Nov 25 14:30:57 UTC 2021
On 11/25/21 5:42 AM, Piotr Oniszczuk wrote:
> Peter,
> Why not to go with ffmpeg as git subproject of mythv?
> With capability of optional ffmpeg git hash declaration at i.e. myth config stage?
> In myth releases we can go ffmpeg tags (so no any config variables) - but for any ffmpeg bisecting or experiments or even forking (absolutely to avoid but you know life is life......)
I had looked at this before. I am not experienced with advanced git
usage like subprojects. From what I could find out there would be a
problem with the build process, because a git clone or pull of the
mythtv project would not get the ffmpeg code, there had to be a separate
git command to refresh the FFmpeg directory in MythTV. There may be a
way but I could not figure it out.
My thinking is now that we can stop using the MythTV/FFmpeg repository.
For each new resync just copy the code from the latest tag of
FFmpeg/FFmpeg into MythTV/external/FFmpeg and apply our patches to that.
For bisecting FFmpeg we will need to bisect in the FFmpeg repository,
then copy and apply patches for each test.
If you have details of a better way please let me know. How would the
subproject work? Would we still use the MythTV/FFmpeg repository? How
would the pull or clone work to get the subproject code pulled into the
main code structure?
Peter
More information about the mythtv-dev
mailing list