Substituting a custom x264 build

HandBrake for Mac support
Forum rules
An Activity Log is required for support requests. Please read How-to get an activity log? for details on how and why this should be provided.
Post Reply
b8zs
Posts: 1
Joined: Fri Feb 23, 2007 1:25 am

Post by b8zs »

if we have a custom compiled x264 binary, how can we replace the version MediaFork uses?
jbrjake
Veteran User
Posts: 4805
Joined: Wed Dec 13, 2006 1:38 am

Post by jbrjake »

b8zs wrote:if we have a custom compiled x264 binary, how can we replace the version MediaFork uses?
We don't use an executable binary of x264, we utilize libx264.a.

If you're only interested in the CLI, you can build with jam, that'll make this a lot easier. You can just put your customized source tar.gz up on an FTP site somewhere and change the x264 version.txt file in the contrib directory, then jam. It'll download and compile it.

If you want this in the GUI, you're going to have to go through a lot more work, because the Mac app uses universal binaries prigaux builds, which it downloads precompiled in one package. You'll have to open it up, replace the libx264 with your own build (it'll have to be universal or xcode will barf i think), repackage, and change the URL in the contrib download shell script in the main source directory to one where you'll host it.

May I ask what kind of customizations your build of x264 has over the latest official revision?
prigaux
Experienced
Posts: 94
Joined: Mon Jan 01, 2007 3:25 pm

Post by prigaux »

Just a little correction, the jam will build the CLI, the GUI and the dylib too but only single architecture.

Philippe
Post Reply