Difference between revisions of "Win32Compile"

From VideoLAN Wiki
Jump to navigation Jump to search
Line 1: Line 1:
== Before you start ==
+
Compile VLC for Windows<br>
 +
 
 +
 
 +
== Before you start ==
  
 
One common desire that leads people to want to rebuild VLC is to "rebuild a debug version" or "add printf()s", but this is not strictly necessary, as VLC includes a debug logging feature by default. If you are using a binary release (or have already built VLC), just run <code>'vlc.exe'</code> and select "Messages..." from the "Tools" menu.  
 
One common desire that leads people to want to rebuild VLC is to "rebuild a debug version" or "add printf()s", but this is not strictly necessary, as VLC includes a debug logging feature by default. If you are using a binary release (or have already built VLC), just run <code>'vlc.exe'</code> and select "Messages..." from the "Tools" menu.  
Line 7: Line 10:
 
To store a debug log of the current VLC session, you can use <code>'vlc -vvv --extraintf=logger'</code>. You will end-up with a <code>vlc-log.txt</code> file in your current directory.  
 
To store a debug log of the current VLC session, you can use <code>'vlc -vvv --extraintf=logger'</code>. You will end-up with a <code>vlc-log.txt</code> file in your current directory.  
  
== Building VLC from source ==
+
== Building VLC from source ==
  
 
If you want to build VLC from source, you have several choices:  
 
If you want to build VLC from source, you have several choices:  
Line 32: Line 35:
 
| None  
 
| None  
 
| '''Not advised.'''  
 
| '''Not advised.'''  
Even though VLC includes some MSVC project files, this method is advised only if you just want to experiment/play with some basic functionality in VLC. VLC depends on a lot of third-party libraries and building them in MSVC is inconvenient (and in some cases, impossible). <br> If you want to run VLC under the MSVC debugger, use <code>--fast-mutex --win9x-cv-method=1</code> because the debugger usually loses signals sent by PulseEvent().
+
Even though VLC includes some MSVC project files, this method is advised only if you just want to experiment/play with some basic functionality in VLC. VLC depends on a lot of third-party libraries and building them in MSVC is inconvenient (and in some cases, impossible). <br> If you want to run VLC under the MSVC debugger, use <code>--fast-mutex --win9x-cv-method=1</code> because the debugger usually loses signals sent by PulseEvent().  
  
 
|}
 
|}
  
== Obtaining the build tools ==
+
== Obtaining the build tools ==
  
 
Each build method requires its own toolchain:  
 
Each build method requires its own toolchain:  
Line 70: Line 73:
 
<pre>tar jxf contrib-20061122-win32-bin-gcc-3.4.5-only.tar.bz2 -C /
 
<pre>tar jxf contrib-20061122-win32-bin-gcc-3.4.5-only.tar.bz2 -C /
 
</pre>  
 
</pre>  
(Note the <code>"-C /"</code>!)
+
(Note the <code>"-C /"</code>!)  
  
 
== Configuring the build  ==
 
== Configuring the build  ==
  
Once you've got all the files you need in place, you need to configure the build with the <code>configure</code> script.
+
Once you've got all the files you need in place, you need to configure the build with the <code>configure</code> script.  
  
Good examples can be found in some files:<br>
+
Good examples can be found in some files:<br>  
 
<pre>extras/package/win32/configure-mingw.sh
 
<pre>extras/package/win32/configure-mingw.sh
  
 
extras/package/win32/configure-msys.sh
 
extras/package/win32/configure-msys.sh
  
extras/package/win32/configure-comon.sh</pre>
+
extras/package/win32/configure-comon.sh</pre>  
See <code>'./configure --help'</code> for more information.
+
See <code>'./configure --help'</code> for more information.  
  
== Building VLC ==
+
== Building VLC ==
  
 
Once configured, to build VLC, just run <code>'make'</code>.  
 
Once configured, to build VLC, just run <code>'make'</code>.  
Line 105: Line 108:
 
|}
 
|}
  
'''''Well done—you're ready to use VLC!'''''
+
'''''Well done—you're ready to use VLC!'''''  
 
 
 
 
  
 
[[Category:Building]]
 
[[Category:Building]]

Revision as of 13:21, 13 June 2010

Compile VLC for Windows


Before you start

One common desire that leads people to want to rebuild VLC is to "rebuild a debug version" or "add printf()s", but this is not strictly necessary, as VLC includes a debug logging feature by default. If you are using a binary release (or have already built VLC), just run 'vlc.exe' and select "Messages..." from the "Tools" menu.

You can also run VLC from the Windows command-line interpreter, cmd.exe (a.k.a. "DOS window"), in which case you'll be able to use the command-line arguments. You can obtain a list of these command line arguments by typing 'vlc --help' or 'vlc --help --advanced'.

To store a debug log of the current VLC session, you can use 'vlc -vvv --extraintf=logger'. You will end-up with a vlc-log.txt file in your current directory.

Building VLC from source

If you want to build VLC from source, you have several choices:

Method Documentation Notes
Cross-compile with Mingw32 on Linux None Preferred method (uses cross compilation)
Native-compile with MSYS+MINGW Win32CompileMSYSNew Preferred native compilation method. MSYS is a minimal build environment to compile Unixish projects under Microsoft Windows. It provides all the commonly-required Unix tools (like sh, gmake, and so forth).
Native-compile with Cygwin Win32CompileCygwinNew OUTDATED native compilation method
Native-compile with Microsoft Visual C++ None Not advised.

Even though VLC includes some MSVC project files, this method is advised only if you just want to experiment/play with some basic functionality in VLC. VLC depends on a lot of third-party libraries and building them in MSVC is inconvenient (and in some cases, impossible).
If you want to run VLC under the MSVC debugger, use --fast-mutex --win9x-cv-method=1 because the debugger usually loses signals sent by PulseEvent().

Obtaining the build tools

Each build method requires its own toolchain:

Method Notes
Cross-compile with mingw32 on GNU/Linux
  • Debian/Ubuntu users can apt-get install mingw32 mingw32-binutils, however building FFmpeg now requires mingw32-runtime >= 3.15 and w32api >= 3.13 so these will have to be updated manually.
  • Gentoo users can emerge crossdev && crossdev mingw32
  • Other systems may attempt http://www.mingw.org/wiki/LinuxCrossMinGW
Native-compile with MSYS+MINGW Read the documentation
Native-compile with Cygwin Read the documentation

3rd party libraries.

VLC modules requires numerous open source projects to work (like AC3 audio decoding or MPEG-4 video decoding).

If you feel you must build these libraries from source, go to extras/contrib and read the README.

If you want to save yourself a lot of time and energy, use the pre-built versions of these libraries. You may download them from http://people.videolan.org/~jb/Contribs/, named in fashion of contrib-yyyymmdd-win32-version-bin-gcc-gccversion-only.tar.bz2.

Install the pre-built libraries into the standard directories (/usr/win32/*) by using

tar jxf contrib-20061122-win32-bin-gcc-3.4.5-only.tar.bz2 -C /

(Note the "-C /"!)

Configuring the build

Once you've got all the files you need in place, you need to configure the build with the configure script.

Good examples can be found in some files:

extras/package/win32/configure-mingw.sh

extras/package/win32/configure-msys.sh

extras/package/win32/configure-comon.sh

See './configure --help' for more information.

Building VLC

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:

Command Description
make package-win32-base Creates a subdirectory named vlc-x.x.x with all the binaries 'stripped' (that is, smallest size, unusable with a debugger)
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 must have NSIS installed in its default location for this to work.

Well done—you're ready to use VLC!