Installing the dependencies from the package or portage system is generally much easier and faster. You should use only one method at a time: There are a several ways to get those libraries. On RPM distributions, they usually end in -devel.īe careful! If the libraries are not provided by your distribution, you may be better off linking VLC with them statically. On Debian/Ubuntu, the correct package names end with -dev.
Furthermore keep in mind that whilst build a program (in this case, VLC), you need to install the development packages (development header files and import libraries), not just the run-time libraries. If you fail to install a required library, either the configure script or (more likely) you will end up with a crippled VLC program. You must install and enable all the necessary underlying libraries. But first, you need to make sure that all the required dependencies are in place. Now you can almost configure the VLC build. If you are using an official release, download source code, extract the archive and go into the resulting VLC directory, e.g.: $ git clone git:///vlc.git $ cd vlcīootstrapping will fail if 'autotools' is missing or out-of-date. If you are using the Git development version, start by bootstrapping the source tree: Start by getting the source, using FTP for official releases, or using Git to track VLC development. $ sudo pacman -S base-devel git pkg-config autoconf automake
$ sudo apt-get install git g++ make libtool automake autopoint pkg-config flex bison lua5.2 Make sure they are up-to-date and usable for your system. If you build from the Git repositories, you will also need the GNU build system, also known as the "autotools" (autoconf, automake, libtool and gettext) to setup the Makefiles. Gcc (version 4.9 or later) is recommended, but clang/LLVM are known to work as well. VLC requires a C11 compiler, development headers and a toolchain.
0 kommentar(er)
