From owner-freebsd-multimedia@FreeBSD.ORG  Mon Mar  3 11:48:35 2014
Return-Path: <owner-freebsd-multimedia@FreeBSD.ORG>
Delivered-To: freebsd-multimedia@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 92A6E642;
 Mon,  3 Mar 2014 11:48:35 +0000 (UTC)
Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com
 [IPv6:2a00:1450:4010:c04::22d])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id E611AE3E;
 Mon,  3 Mar 2014 11:48:34 +0000 (UTC)
Received: by mail-lb0-f173.google.com with SMTP id p9so4532310lbv.18
 for <multiple recipients>; Mon, 03 Mar 2014 03:48:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=googlemail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=xHFJtiPyf9Ni/fMHsjZmaKcZQjhBcWxOunzw1xu46BE=;
 b=r0w6OM6BcZbAwPP0WwEEuBUTy4KGG5HIPfZLE0qbkcPAeiks+KeCLmPtdMLPabkbR9
 c5qnTFDKLYa1Pyvd4p6GXLuai5bJpnIxdiBvs1JHb6pHXiBscjWzKrSujoMnY4TImPg4
 VVJhjQ0LjZeWuFDpxX6Jep1co+N9FqKdJglRr0cAq0oTGGL3c1ibKDWmd4IL+kyzOuNa
 0ssToCnagr7RhsqrRUAAy/Sos4boV0YtVBiqaeZoXRh2/jofVMHa0GP6F1QlrXvqRv/c
 l8OalB2qoYY/IDsGzW5f9MnNTcWysW4eFMYNB2U2YH0kKnBDlXyqpzhOPmcD9lONDsEI
 uvHA==
MIME-Version: 1.0
X-Received: by 10.152.166.198 with SMTP id zi6mr262041lab.73.1393847312987;
 Mon, 03 Mar 2014 03:48:32 -0800 (PST)
Received: by 10.112.35.167 with HTTP; Mon, 3 Mar 2014 03:48:32 -0800 (PST)
In-Reply-To: <5312C4F4.7060109@my.hennepintech.edu>
References: <5312C4F4.7060109@my.hennepintech.edu>
Date: Mon, 3 Mar 2014 11:48:32 +0000
Message-ID: <CAFHbX1+avUwj4BKQsuUnA4A4fh+9wp5W_ZWRSw1QKWTXbvfXxQ@mail.gmail.com>
Subject: Re: FFmpeg and x264 circular dependency
From: Tom Evans <tevans.uk@googlemail.com>
To: Andrew Berg <aberg010@my.hennepintech.edu>
Content-Type: text/plain; charset=UTF-8
Cc: freebsd-multimedia@freebsd.org, koobs@freebsd.org
X-BeenThere: freebsd-multimedia@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multimedia discussions <freebsd-multimedia.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-multimedia>, 
 <mailto:freebsd-multimedia-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-multimedia/>
List-Post: <mailto:freebsd-multimedia@freebsd.org>
List-Help: <mailto:freebsd-multimedia-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia>, 
 <mailto:freebsd-multimedia-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Mar 2014 11:48:35 -0000

On Sun, Mar 2, 2014 at 5:43 AM, Andrew Berg
<aberg010@my.hennepintech.edu> wrote:
> What would it take to separate libav into its own port? I realize the change would be disruptive, but it seems a lot cleaner than keeping it
> bundled with FFmpeg, even if FFmpeg bundles libav upstream, and it would solve this issue and potentially some similar issues with other
> ports that use libav. There is a separate git repository for libav[1], however, I do not know how well it works with the rest of FFmpeg[2].

libav is not ffmpeg, it is a fork of ffmpeg*, so that is a non starter.

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).

Cheers

Tom

* I know that "libav" is the api of ffmpeg, but "git.libav.org" is NOT
ffmpeg, it is "libav", the fork of ffmpeg. So confusing..