Changes between Version 100 and Version 101 of CompilationGuide/Ubuntu
- Timestamp:
- Aug 19, 2014, 9:53:18 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CompilationGuide/Ubuntu
v100 v101 48 48 An assembler for x86 optimizations used by x264 and FFmpeg. Highly recommended or your resulting build may be very slow. 49 49 50 If your repository offers a `yasm` package ≥ 1. 2.0 then you can install that instead of compiling:50 If your repository offers a `yasm` package ≥ 1.3.0 then you can install that instead of compiling: 51 51 52 52 {{{ … … 58 58 {{{ 59 59 cd ~/ffmpeg_sources 60 wget http://www.tortall.net/projects/yasm/releases/yasm-1. 2.0.tar.gz61 tar xzvf yasm-1. 2.0.tar.gz62 cd yasm-1. 2.060 wget http://www.tortall.net/projects/yasm/releases/yasm-1.3.0.tar.gz 61 tar xzvf yasm-1.3.0.tar.gz 62 cd yasm-1.3.0 63 63 ./configure --prefix="$HOME/ffmpeg_build" --bindir="$HOME/bin" 64 64 make … … 69 69 === libx264 === 70 70 71 H.264 video encoder. See the [[ x264EncodingGuide|x264 Encoding Guide]] for more information and usage examples.71 H.264 video encoder. See the [[Encode/H.264|H.264 Encoding Guide]] for more information and usage examples. 72 72 73 73 Requires `ffmpeg` to be configured with `--enable-gpl` `--enable-libx264`. … … 86 86 === libfdk-aac === 87 87 88 AAC audio encoder. See the [[ AACEncodingGuide|AAC Encoding Guide]] for more information and usage examples.88 AAC audio encoder. See the [[Encode/AAC|AAC Encoding Guide]] for more information and usage examples. 89 89 90 90 Requires `ffmpeg` to be configured with `--enable-libfdk_aac` (and `--enable-nonfree` if you also included `--enable-gpl`). … … 218 218 === Persistent Environment Variables === 219 219 220 You can tell your shell (assuming you're using Bash) to persist antly use your new `ffmpeg` in `~/bin`. The first command will allow you to simply run `man ffmpeg` to get the FFmpeg man pages. The second command will source `~/.profile` which will add `~/bin` to your `$PATH`. In short, the following commands will allow you to simply type `ffmpeg` and `man ffmpeg` in your terminal and they will "just work":220 You can tell your shell (assuming you're using Bash) to persistently use your new `ffmpeg` in `~/bin`. The first command will allow you to simply run `man ffmpeg` to get the FFmpeg man pages. The second command will source `~/.profile` which will add `~/bin` to your `$PATH`. In short, the following commands will allow you to simply type `ffmpeg` and `man ffmpeg` in your terminal and they will "just work": 221 221 222 222 {{{ … … 240 240 === Additional Notes === 241 241 242 * See the [[ x264EncodingGuide|x264 Encoding Guide]] for some encoding examples.242 * See the [[Encode/H.264|H.264 Encoding Guide]] for some encoding examples. 243 243 * If you do not see `FFmpeg developers` in your ffmpeg console output then something went wrong and you're probably using the [http://stackoverflow.com/a/9477756/1109017 fake "ffmpeg"] from the repository. 244 244 * HTML formatted documentation is available in `~/ffmpeg_build/share/doc/ffmpeg`. … … 279 279 280 280 == Also See == 281 * [[ GenericCompilationGuide|Generic FFmpeg Compilation Guide]]282 * [[ x264EncodingGuide|x264 Encoding Guide]]283 * [[ AACEncodingGuide|AAC Encoding Guide]]281 * [[CompilationGuide/Generic|Generic FFmpeg Compilation Guide]] 282 * [[Encode/H.264|H.264 Encoding Guide]] 283 * [[Encode/AAC|AAC Encoding Guide]]
