Run the following command to open Nano at the line in question: faac-1.28# nano +126 common/mp4v2/mpeg4ip.h Now – before finishing off faac, you need to check and possibly edit a line of code in one of the headers (for v1.28 you need to do this, other versions may not require this). Lame-3.99# make install Install FAAC audio support (one possible AAC support) lame-3.99# cd ~/srcs
X264# make install Install Lame audio support (for mp3 audio) x26x# cd ~/srcs Install supporting Libraries and Build tools ~# apt-get install libasound2-dev build-essential make autoconf libtool Install x264 video support ~# cd ~/srcs This can shave minutes or even hours of the compilation of some packages. Using the -j switch to allocate more cores gives a slight boost in compilation speed, as work is shared across more than one processor core. If you are using an original Pi, Pi+, Model A or Zero for this, you should remove the -j3 switch when executing the command. You will also notice the usage of the “-j3” switch on the “make” commands – this tells the ‘make’ tool to use 3 processor cores of the 4-cored Pi2/Pi3. This guide will assume that the following path: “/home/pi/srcs” exists already. I usually create a directory called “srcs” in my home directory for when I am downloading and building packages from source code. ~# apt-get install git & apt-get install svn Source downloads You’ll be getting some files from source, so it’s always best to have GIT and SVN installed. From my experience some builds can be flaky when done using the sudo command.
If you’re doing this on the Raspberry Pi, I would encourage you to run the following commands as root, so enter “su” in the command prompt and switch to the root user. Here’s my recipe for building and compiling FFmpeg for the Raspbian Jessie environment for Raspberry Pi. There’s plenty of guides around, but none that worked flawlessly for me.
0 kommentar(er)
