From: Jean-Baptiste Kempf <jb@videolan.org>
Date: Thu, 6 Mar 2008 06:55:09 +0000 (-0800)
Subject: Make clear of what compilation is supported and which one is not for Windows.
X-Git-Tag: 0.9.0-test0~2292
X-Git-Url: https://git.sesse.net/?a=commitdiff_plain;h=8d0a3a2da87cebfda1212dea51aa596f317b1145;hp=1bed9134fd910318a296874f78a1bf551bfa39f4;p=vlc

Make clear of what compilation is supported and which one is not for Windows.
---

diff --git a/INSTALL.win32 b/INSTALL.win32
index bf949711b8..432dc86482 100644
--- a/INSTALL.win32
+++ b/INSTALL.win32
@@ -31,6 +31,13 @@ If you want to build VLC from sources, you can do it in several ways:
   NOTE: This is the PREFERRED way of building VLC natively (the others
   are not as much tested so expect more difficulties with them).
 
+  Read http://wiki.videolan.org/Win32CompileCygwinNew to have a complete HOWTO
+
+- On GNU/Linux, using the mingw32 cross-compiler.
+  This method is  preferred over all the others.
+
+UNSUPPORTED METHODS
+-------------------
 - natively on Windows, using MSYS+MINGW (www.mingw.org)
   (MSYS is a minimal build environment to compile Unixish projects under
   windoze. It provides all the common Unix tools like sh, gmake...)
@@ -46,9 +53,6 @@ If you want to build VLC from sources, you can do it in several ways:
     with the --fast-mutex --win9x-cv-method=1 options because the debugger
     usually loses signals sent by PulseEvent() )
 
-- or on GNU/Linux, using the mingw32 cross-compiler.
-  This method is  preferred over all the others.
-
 Getting the right compiler tools
 ================================