Changes between Version 3 and Version 4 of CompilationGuide/Haiku


Ignore:
Timestamp:
Apr 11, 2015, 6:56:25 AM (4 years ago)
Author:
Timothy_Gu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CompilationGuide/Haiku

    v3 v4  
    1717== Installing required components == 
    1818 
     19For x86 GCC 2 hybrid image: 
     20 
    1921{{{ 
    20 #!shell 
    21 pkgman install git 
    22 pkgman install yasm 
     22#!sh 
     23pkgman install lame_x86_devel libtheora_x86_devel libvorbis_x86_devel libvpx_x86_devel speex_x86_devel yasm 
    2324}}} 
     25 
     26For x86 GCC 4 (hybrid and otherwise) and x86-64 images: 
     27 
     28{{{ 
     29#!sh 
     30pkgman install lame_devel libtheora_devel libvorbis_devel libvpx_devel speex_devel yasm 
     31}}} 
     32 
     33The dependencies above are only the dependencies available from the binary distribution. If you would like to have more features, feel free to use `haikuporter` to build more, although success is not guaranteed. 
     34 
     35In particular, x264, x265, and Opus encoding support is only available by building the packages yourself. 
     36 
     37== Getting FFmpeg source == 
     38 
     39If you are running Haiku in a VM, then you probably should consider NOT to clone the repo with Git, but instead get the snapshot: 
     40 
     41With Git metadata: https://ffmpeg.org/releases/ffmpeg-snapshot-git.tar.bz2 
     42Without: https://ffmpeg.org/releases/ffmpeg-snapshot.tar.bz2 
     43 
     44If performance is not a concern then you can simply: 
     45 
     46{{{ 
     47#!sh 
     48git clone git://source.ffmpeg.org/ffmpeg.git ffmpeg 
     49}}} 
     50 
     51 
     52== Setting `$PATH` == 
     53 
     54As mentioned above, you will need to set `$PATH` variable to give GCC 4 toolchain priority over the legacy GCC 2 stack, on an x86 GCC 2 hybrid build. To do so, execute the following in your shell: 
     55 
     56{{{ 
     57#!sh 
     58export PATH="/system/bin/x86:$PATH" 
     59}}} 
     60 
     61This is NOT necessary on x86-64. You also might want to put this into your `~/.profile` if you will be building FFmpeg regularly. 
     62 
     63== Configuring == 
     64 
     65It is NOT recommended to install ffmpeg system-wide, as it is very possible that it would break the system installation, upon which the default web browser WebPositive is depended. In the following configuration, binaries and development files are installed to `/boot/home/ffmpeg-installed` to avoid conflict, while man pages are installed to the standard directory.  
     66 
     67{{{ 
     68#!sh 
     69cd ffmpeg 
     70prefix='/boot/home/ffmpeg-installed' 
     71./configure \ 
     72    --prefix="$prefix" \ 
     73    --bindir="$prefix/bin/" \ 
     74    --datadir="$prefix/data/" \ 
     75    --incdir="$prefix/develop/headers" \ 
     76    --libdir="$prefix/develop/lib" \ 
     77    --mandir='/system/documentation/man/' \ 
     78    --enable-libmp3lame \ 
     79    --enable-libvorbis \ 
     80    --enable-libspeex \ 
     81    --enable-libtheora \ 
     82    --enable-libvpx \ 
     83    --enable-gpl 
     84}}} 
     85