Changeset 333e8400
- Timestamp:
- 10/06/2014 01:39:49 AM (10 years ago)
- Branches:
- kde5-14686, systemd-13485
- Children:
- 37dfd42
- Parents:
- 3cf61ed8
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
multimedia/videoutils/ffmpeg.xml
r3cf61ed8 r333e8400 7 7 <!ENTITY ffmpeg-download-http "http://ffmpeg.org/releases/ffmpeg-&ffmpeg-version;.tar.bz2"> 8 8 <!ENTITY ffmpeg-download-ftp " "> 9 <!ENTITY ffmpeg-md5sum " c36caa8d29b3677dcb7bd8c546890c9d">9 <!ENTITY ffmpeg-md5sum "9e6163b09b7b9331b834d80874c2c0ff"> 10 10 <!ENTITY ffmpeg-size "7.1 MB"> 11 <!ENTITY ffmpeg-buildsize "130 MB (additional 8 70 MB for docs and 1903MB to run the FATE tests)">12 <!ENTITY ffmpeg-time "3.5 SBU (additional 0.9 SBU for docs and 5SBU to run the FATE tests, after sample files are downloaded)">11 <!ENTITY ffmpeg-buildsize "130 MB (additional 866 MB for docs and 1902 MB to run the FATE tests)"> 12 <!ENTITY ffmpeg-time "3.5 SBU (additional 1.1 SBU for docs and 4.8 SBU to run the FATE tests, after sample files are downloaded)"> 13 13 ]> 14 14 … … 205 205 206 206 <para> 207 To properly test the installation you must have <xref linkend="rsync"/> 208 installed and follow the instructions for the 209 <ulink url="http://www.ffmpeg.org/fate.html"> 210 FFmpeg Automated Testing Environment</ulink> (FATE). First, about 879 MB 211 of sample files used to run FATE are downloaded with the command: 212 </para> 213 214 <screen><userinput>make fate-rsync SAMPLES=fate-suite/</userinput></screen> 215 216 <para> 217 The <filename class="directory">fate-suite</filename> directory is 218 created and the files are downloaded there. That command actually runs 219 <command>rsync -vrltLW --timeout=60 --contimeout=60 rsync://fate-suite.ffmpeg.org/fate-suite/ fate-suite/</command> 220 command, thus you may want to compress and keep this directory for 221 testing again, in another system, or when a new version of ffmpeg is 222 launched. Then, you unpack the sample files in the source directory, and 223 run, again, the <command>make</command> command above, to sync with the 224 repository. Now, the download size and time are drastically reduced. 225 Estimated values in "Package Information" do not include the download 226 SBU. Next, FATE is executed, with the commands (you obtain a number of 227 tests greater than 2000): 228 </para> 229 230 <screen><userinput>make fate SAMPLES=fate-suite/ | tee ../fate.log && 231 grep ^TEST ../fate.log | wc -l</userinput></screen> 207 The fate-suite tests include comparisons with installed files, and should 208 not be run before the package is installed. Therefore, if you desire to 209 run them, instructions are given further below. 210 </para> 232 211 233 212 <para> … … 246 225 </para> 247 226 248 <screen role="root"><userinput>install -v -m644 doc/*. 227 <screen role="root"><userinput>install -v -m644 doc/*.pdf \ 249 228 /usr/share/doc/ffmpeg-&ffmpeg-version; && 250 install -v -m644 doc/*.ps 229 install -v -m644 doc/*.ps \ 251 230 /usr/share/doc/ffmpeg-&ffmpeg-version;</userinput></screen> 252 231 … … 262 241 find /usr/share/doc/ffmpeg-&ffmpeg-version;/api -type d -exec chmod -c 0755 "{}" ";"</userinput></screen> 263 242 243 <para> 244 To properly test the installation you must have <xref linkend="rsync"/> 245 installed and follow the instructions for the <ulink 246 url="http://www.ffmpeg.org/fate.html"> FFmpeg Automated Testing 247 Environment</ulink> (FATE). First, about 879 MB of sample files used to 248 run FATE are downloaded with the command: 249 </para> 250 251 <screen><userinput>make fate-rsync SAMPLES=fate-suite/</userinput></screen> 252 253 <para> 254 The <filename class="directory">fate-suite</filename> directory is 255 created and the files are downloaded there. That command actually runs 256 <command>rsync -vrltLW --timeout=60 --contimeout=60 257 rsync://fate-suite.ffmpeg.org/fate-suite/ fate-suite/</command> command, 258 thus you may want to compress and keep this directory for testing again, 259 in another system, or when a new version of ffmpeg is launched. Then, you 260 unpack the sample files in the source directory, and run, again, the 261 <command>make</command> command above, to sync with the repository. Now, 262 the download size and time are drastically reduced. Estimated values in 263 "Package Information" do not include the download SBU. Next, FATE is 264 executed, with the commands (you obtain a number of tests greater than 265 2000): 266 </para> 267 268 <screen><userinput>make fate SAMPLES=fate-suite/ | tee ../fate.log && 269 grep ^TEST ../fate.log | wc -l</userinput></screen> 270 264 271 </sect2> 265 272 … … 285 292 286 293 <para> 294 <option>--enable-libfreetype</option>: Enables 295 <application>Freetype</application> support. 296 </para> 297 298 <para> 287 299 <parameter>--enable-gpl</parameter>: Enables the use of GPL code and 288 300 permits support for postprocessing, swscale and many other features. … … 295 307 296 308 <para> 297 <parameter>--enable-nonfree</parameter>: Enables the use of nonfree 298 code. Note that the resulting libraries and binaries will be 299 unredistributable. 309 <parameter>--enable-nonfree</parameter>: Enables the use of nonfree code. 310 Note that the resulting libraries and binaries will be unredistributable. 300 311 </para> 301 312 … … 304 315 305 316 <para> 306 <parameter>--enable-shared</parameter>: Enables building shared libraries,307 otherwise only static libraries are built and installed.317 <parameter>--enable-shared</parameter>: Enables building shared 318 libraries, otherwise only static libraries are built and installed. 308 319 </para> 309 320 … … 325 336 326 337 <para> 327 <parameter>--enable-libmp3lame</parameter>: Enables MP3 audio encoding via328 <filename class="libraryfile">libmp3lame</filename>.338 <parameter>--enable-libmp3lame</parameter>: Enables MP3 audio encoding 339 via <filename class="libraryfile">libmp3lame</filename>. 329 340 </para> 330 341 … … 345 356 <parameter>--enable-libx264</parameter>: Enables high-quality 346 357 H.264/MPEG-4 AVC encoding via <filename 347 class="libraryfile">libx264</filename>. 358 class="libraryfile">libx264</filename>.A 348 359 </para> 349 360 … … 353 364 354 365 <para> 355 <command>gcc tools/qt-faststart.c -o tools/qt-faststart</command>: 356 This builds the <command>qt-faststart</command> program which can357 modify QuickTime formatted movies358 (<filename class="extension">.mov</filename> or359 <filename class="extension">.mp4</filename>) so that the header information360 is located at the beginning of the file instead of the end. This allows361 the movie file to begin playing before the entire file hasbeen downloaded.366 <command>gcc tools/qt-faststart.c -o tools/qt-faststart</command>: This 367 builds the <command>qt-faststart</command> program which can modify 368 QuickTime formatted movies (<filename class="extension">.mov</filename> 369 or <filename class="extension">.mp4</filename>) so that the header 370 information is located at the beginning of the file instead of the end. 371 This allows the movie file to begin playing before the entire file has 372 been downloaded. 362 373 </para> 363 374
Note:
See TracChangeset
for help on using the changeset viewer.