Date: Wed, 5 Mar 2014 02:37:56 -0600 From: Andrew Berg <aberg010@my.hennepintech.edu> To: Tom Evans <tevans.uk@googlemail.com> Cc: freebsd-multimedia@freebsd.org, koobs@freebsd.org Subject: Re: FFmpeg and x264 circular dependency Message-ID: <5316E264.8040400@my.hennepintech.edu> In-Reply-To: <CAFHbX1%2BavUwj4BKQsuUnA4A4fh%2B9wp5W_ZWRSw1QKWTXbvfXxQ@mail.gmail.com> References: <5312C4F4.7060109@my.hennepintech.edu> <CAFHbX1%2BavUwj4BKQsuUnA4A4fh%2B9wp5W_ZWRSw1QKWTXbvfXxQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2014.03.03 05:48, Tom Evans wrote: > libav is not ffmpeg, it is a fork of ffmpeg*, so that is a non starter. Okay, that clears some things up. > Option 4, not on your list, is to build an ffmpeg locally just for > x264 to link to. libx264 can build with whatever options you want, > building whatever parts of ffmpeg is requires, and the > presence/non-presence of ffmpeg would not affect the build of libx264. > This is how other projects that use parts of ffmpeg do it (eg, > mythtv). If I understand this correctly, this is essentially option 1 with a workaround that requires the user to keep that local copy up-to-date manually instead of using ports.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5316E264.8040400>