readme.txt. Added additional info about dependencies and project generator.

SMP/readme.txt

 
 This is a small list of steps in order to build FFmpeg into a msvc DLL and lib file.
 
-The project contains Release and Debug builds for static lib files (Debug/Release)
+The projects contain Release and Debug builds for static lib files (Debug/Release)
   as well as dynamic shared dll files (DebugDLL/ReleaseDLL).
 Choose whichever project configuration meets your requirements.
 
+*** Using the Default Supplied Projects ***
+
+The supplied project files are created using default configuration options as used by the ShiftMediaProject.
+These projects use Visual Studio 2013 and require certain additional dependencies to be built and available at compile time.
+Required supplied project dependencies include:
+    bzlib
+    iconv
+    zlib
+    lzma
+    sdl
+    libmp3lame
+    libvorbis
+    libspeex
+    libopus
+    libilbc
+    libfdk-aac
+    libtheora
+    libx264
+    libx265
+    libxvid
+    libvpx
+    libgme
+    libmodplug
+    libsoxr
+    libfreetype
+    fontconfig
+    libfribidi
+    libass
+    gnutls
+    librtmp
+    libssh
+    libcdio
+    libbluray
+    opengl
+    opencl
+    nvenc
+
+Most of these dependencies (and there dependencies) are available in the ShiftMediaProject repositories.
+However the following is a list of extra dependency options that require external downloads:
+    1) sdl (requires SDL 1.2)
+		a) Download pre-built binaries from the sdl homepage.
+		b) Extract all the header files into OutputDir/include/SDL*.
+		c) Extract the lib's to OutputDir/lib* and the DLL's to OutputDir/bin*.
+    2) opengl (requires glext)
+		a) Download glext from the glext homepage.
+		b) Extract all the header files into OutputDir/include/gl*.
+    3) opencl (requires Intel or AMD OpenCL SDK, NVIDIAs does not support required features)
+		a) Download either the "Intel OpenCL SDK" or the "AMD OpenCL SDK" from their respective suppliers.
+			Note: The default projects use the Intel SDK.
+		b) Install the downloaded SDK wherever desired.
+		c) If not using the default Intel SDK then re-generate the projects (see below). Project generator will detect 
+            installed SDK's and set paths accordingly.
+    4) nvenc (requires NVIDIA CUDA SDK)
+		a) Download the "NVIDIA CUDA SDK" from the NVIDIA website.
+		b) Install the downloaded SDK wherever desired.
+		c) Download the "NVIDIA Video Codec SDK" from the NVIDIA website.
+		d) Copy 'nvEncodeAPI.h' from the "NVIDIA Video Codec SDK" into the installed %CUDA%\include folder 
+			(where %CUDA% is the location that the CUDA SDK was installed).
+			
+*OutputDir is the "Output Directory" specified in the project properties. 
+    Note: There is a different OutputDir for 32/64bit configurations. Lib's and DLL's should be placed in the correct directory.
+	Any header files will need to be placed in both the 32 and the 64bit OutputDir's.
+	By default the 32bit OutputDir is "..\..\..\msvc32\" and 64bit is "..\..\..\msvc64\" when using the msvc compiler.
+	
+Any dependencies supplied by ShiftMediaProject should be downloaded next to the FFmpeg folder as they will use the same OutputDir
+location. Projects to build each dependency can be found in the respective SMP directories.
+
+The exact options used to build the default supplied projects can be found in 'project_generate_msvc.bat' in the
+project_generate folder. To change these options and generate new projects see the "Generating Custom Project Files"
+section below.
+
+Only dependencies built from supplied ShiftMediaProject repositories are tested and supported. Using compiled dependencies from
+other sources may result in version or other issues. Although these external sources generally work fine any problems associated
+with them are not covered by ShiftMediaProject and so they should be used with discretion.
+
+				
 *** Building with YASM ***
 
-In order to build FFmpeg using msvc you must first download and install YASM.
+In order to build FFmpeg using msvc with assembly support you must first download and install YASM.
 YASM is required to compile all FFmpeg assembly files.
 
 1) Download yasm for Visual Studio from here:
@@ -29,30 +105,38 @@ Currently only up to VS2010 is supported on the web page so just download that.
     b) Replace the 1 occurrence of $(Platform) with win$(PlatformArchitecture)
 
 
-*** Generating custom project files ***
+*** Generating Custom Project Files ***
 
-This project comes with the ffmpeg_generator program which can be used to build a custom project file.
+This project comes with the ffmpeg_generator program which can be used to build custom project files.
 This program accepts many of the configuration parameters that are supported by FFmpegs standard configure script.
-These options can be used to disable/enable specific options that define how ffmpeg is built. Using ffmpeg_generator
+These options can be used to disable/enable specific options that define how FFmpeg is built. Using ffmpeg_generator
 a new project can be built using these options.
 
 To generate a custom project using different configuration options simply build ffmpeg_generator and then run it by
 passing in the desired config options.
 
-The default project is built using standard includes for SMC. For example:
+For example to build FFmpeg without any additional dependencies:
 
-ffmpeg_generator.exe --enable-gpl --enable-version3 --enable-avisynth --enable-nonfree --enable-bzlib --enable-iconv --enable-zlib 
-   --enable-libmp3lame --enable-libvorbis --enable-libspeex --enable-libopus --enable-libfdk-aac --enable-libtheora --enable-libx264 
-   --enable-libxvid --enable-libvpx --enable-libmodplug --enable-libsoxr --enable-libfreetype --enable-fontconfig --enable-libass 
-   --enable-openssl --enable-librtmp --enable-libssh --toolchain=icl --enable-sdl
+ffmpeg_generator.exe --enable-gpl --enable-version3 --disable-bzlib --disable-iconv --disable-zlib 
+    --disable-lzma --disable-sdl --toolchain=msvc
+
+As well as enabling/disabling dependency libraries, specific config options can also be enabled/disabled. For instance a 
+project that does not require yasm can be built by passing --disable-yasm. Specific FFmpeg programs can also be disabled
+such as --disable-ffprobe which will prevent a project file being generated for the FFmpeg program ffprobe.
 
-As well as external libs specific config options can also be enabled/disabled. For instance a project that does not require yasm 
-can be built by passing --disable-yasm.
-To be able to build ffplay the SDL libs must be available in the OutputDir. If you have these libs and wish to use them then sdl
-can be enabled by passing --enable-sdl.
-Specific programs can be ignored such as --disable-ffprobe etc.
 The generator is designed to automatically resolve dependencies so if a configure option is disabled all options that depend on it will 
 also be disabled accordingly.
-By default the generator will build a project using Visual Studio 2013 platform toolsets. These can be changed by hand in the project configuration
-or simply by passing an option to the project generator. The --toolchain= option can be used to change between standard microsoft compiler (msvc)
+
+By default the generator will build a project using the latest available toolchain detected on the host computer. This can be changed by 
+hand in the generated projects properties "Project Configuration->General->Platform Toolset" if an older toolset is desired. The generator 
+also supports use of the Intel compiler. The --toolchain= option can be used to change between standard Microsoft compiler (msvc)
 and the Intel compiler (icl).
+
+Note: FFmpeg requires C99 support in order to compile. Only Visual Studio 2012 or newer supports required C99 functionality and so any 
+older version is not supported. Visual Studio 2013 or newer is recommended. If using an older unsupported version of Visual Studio the
+Intel compiler can be used to add in the required C99 capability.
+
+To be able to build ffplay the SDL libs must be available in the OutputDir. If SDL is disabled then ffplay will also be disabled.
+
+The project generator will also check the availability of dependencies. Any enabled options must have the appropriate headers installed
+in OutputDir (see "Using the Default Supplied Projects" for default OutputDir locations) otherwise an error will be generated.