-INSTALL file for vlc, the VideoLAN Client
+$Id: INSTALL,v 1.24 2003/02/02 04:01:29 sam Exp $
+INSTALL file for the VLC media player
-Configuring VideoLAN
-====================
-A typical way to configure vlc is:
+Configuring VLC
+===============
+
+A typical way to configure VLC is:
./configure --prefix=/usr --enable-gnome
See `./configure --help' for more information.
-Here is a shortcut to copy-paste for a complete build:
-
- make distclean ; ./configure --prefix=/usr --enable-gnome \
- --enable-fb --with-glide --with-ggi --enable-esd --enable-qt
-
If you intend to debug stuff, you may want to compile with debugging
symbols:
- make distclean ; ./configure --prefix=/usr --enable-gnome \
- --enable-fb --with-glide --with-ggi --enable-esd --enable-qt \
- --enable-debug
+ make distclean ; ./configure --prefix=/usr --enable-gnome --enable-debug
-It is also possible to cross-compile for the Win32 platform using mingw32:
- make distclean ; CC=i586-mingw32msvc-gcc CFLAGS=-I/usr/i586-mingw32msvc \
- RANLIB=i586-mingw32msvc-ranlib WINDRES=i586-mingw32msvc-windres \
- ./configure --host=i386-mingw32msvc --with-directx-path=<path> \
- --with-sdl-config-path=<path> --with-gtk-config-path=<path>
-
-
-Building VideoLAN
-=================
+Building VLC
+============
Have a look at the generated Makefile.opts file, you may want to choose
which modules will be compiled as plugins, and which ones will remain in
the core application. The configure script tries to guess for you.
-Once configured, run `make' to build vlc.
+Once configured, run `make' to build VLC.
-Installing and running VideoLAN
-===============================
+Installing and running VLC
+==========================
-You can install the vlc and its plugins by typing:
+You can install the VLC and its plugins by typing:
make install
-But you don't need to install it if you don't want to; vlc can be launched
+But you don't need to install it if you don't want to; VLC can be launched
from the current directory as well:
./vlc
projects / vlc / blobdiff