-If you are cross-compiling from Debian, you can use something
-along those lines:
-
- ./bootstrap; \
- CC=i586-mingw32msvc-gcc \
- ./configure --host=i586-mingw32msvc --build=i386-linux \
- --with-gtk-config-path=/usr/local/gtk-win32/bin \
- --with-sdl-config-path=/usr/local/SDL-1.2.3-win32/i386-mingw32msvc/bin \
- --with-directx=/usr/local/dxheaders \
- --with-dvdcss-tree=../libdvdcss-win
-
-If you are cross-compiling using the mingw32 package provided by
-www.videolan.org, you have to use something along those lines:
-
- ./bootstrap; \
- CC=i586-mingw32msvc-gcc \
- PATH=/usr/local/cross-tools/bin:$PATH \
- ./configure --host=i586-mingw32msvc --build=i386-linux \
- --with-gtk-config-path=/usr/local/gtk-win32/bin \
- --with-sdl-config-path=/usr/local/SDL-1.2.3-win32/i386-mingw32msvc/bin \
- --with-directx=/usr/local/dxheaders \
- --with-dvdcss-tree=../libdvdcss-win
-
-If you are compiling natively on Windoze, then you can use something
-along those lines:
- ./bootstrap; \
- ./configure \
- --with-gtk-config-path=/c/dev/gtk-win32/bin \
- --with-sdl-config-path=/c/dev/SDL-1.2.3-win32/i386-mingw32msvc/bin \
- --with-directx=/c/dev/dxheaders \
- --with-dvdcss-tree=../libdvdcss-win
-
-If you are using cygwin, you can build vlc with or without the unix emulation
-layer (without is usually better). To build without the emulaion layer, use
-something like this:
- ./bootstrap; \
- CC="gcc -mno-cygwin" \
- ./configure \
- --with-gtk-config-path=/cygdrive/c/dev/gtk-win32/bin \
- --with-sdl-config-path=/cygdrive/c/dev/SDL-1.2.3-win32/i386-mingw32msvc/bin \
- --with-directx=/cygdrive/c/dev/dxheaders \
- --with-dvdcss-tree=../libdvdcss-win
-If you want to use the emulation layer, then just omit the CC="gcc -mno-cygwin"
-line.
-
-Note: when using the --with-dvdcss-tree you need to compile the tree
-beforehand.
-
-Building VideoLAN Client
-========================
-
-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, to build vlc you have to:
-
-If you are cross-compiling from Debian or compiling natively on Windoze,
-then just run `make'.
-
-If you are cross-compiling using the mingw32 package provided by
-www.videolan.org, run `PATH=/usr/local/cross-tools/bin:$PATH make'.
-
-Building Win32 interface with bcc32 (Borland's compiler)
-========================================================
-(This stage is only necessary if you want to use the Win32 native interface.
- If you are happy with the GTK interface, then you can skip this section)
-
-1) Compile vlc as usual.
-
-2) From the plugin\win32 directory, use Borland C++ command-line tools
-as follows:
-bpr2mak intfwin.bpr -s \
- | sed 's#^LIBPATH = .*#&;$$(RELEASELIBPATH)# ; s#^USERDEFINES = .*#& -DWIN32 -D__PLUGIN__ -DMODULE_NAME_IS_intfwin -DMODULE_NAME=intfwin#' \
- > intfwin.mak // Create a makefile from intfwin.bpr
-make -fintfwin // It's Borland's make utility !
-
-3) This should create a intfwin.so
-You can remove any other generated file.
-
-
-Well done, now you're ready to use vlc!
+
+Actually Compiling the VLC source
+=================================
+
+Once configured, to build VLC, just run `make'.
+
+Once the compilation is done, you can either run VLC directly from the source
+tree or you can build self-contained VLC packages with the following
+'make' rules:
+
+ make package-win-base
+ will create a subdirectory named vlc-x.x.x with all the binaries
+ 'stripped' (ie. without any debugging symbols).
+
+ make package-win32-zip
+ Same as above but will package the directory in a zip file.
+
+ make package-win32
+ Same as above but will also create an auto-installer package. You will need
+ to have NSIS installed in its default location for this to work.
+
+Well done, now you're ready to use VLC!