--- libgig/trunk/README	2017/11/25 01:19:10	3370
+++ libgig/trunk/README	2021/05/09 10:37:39	3878
@@ -61,6 +61,12 @@
 
 Requirements
 ============
+
+  All systems
+  -----------
+
+  Since libgig 4.3.0 you need at least a C++11 compliant compiler.
+
   POSIX systems (e.g. Linux, macOS):
   ---------------------------------
 
@@ -94,11 +100,23 @@
   ------------------------
 
   libgig was written to compile for any operating system, using standard C
-  library functions. However the latest versions of libgig lack a portable
-  implementation of one tiny method called RIFF::File::ResizeFile(). So you
-  would either have to add native OS API calls for that particular method,
-  that is dependant to your OS, or you have to add a portable
-  implementation. No matter which way you choose, please let us know! :)
+  library functions. However there are some OS dependent requirements:
+
+  * Since libgig 3.0.0 an OS dependent implementation for a tiny method called
+    RIFF::File::ResizeFile() is required. So you would either have to add
+    native OS API calls for that particular method, that is dependant to your
+    OS, or you have to add a portable implementation. No matter which way you
+    choose, please let us know! :)
+
+  * Since libgig 4.3.0 presence of some UUID generating function is required to
+    be provided by the underlying system. This was an optional feature in
+    previous versions of libgig for many years, its absence only meant that you
+    were unable to load gig files created/modified by libgig to be accepted by
+    Tascam's original GigaStudio studio software, did not mean any restriction
+    for being used with LinuxSampler though. This has changed in the meantime,
+    so this is now a hard build requirement, as you would potentially encounter
+    misbehaviours now even if you stay entirely in the Linux eco system if UUIDs
+    were missing in gig files.
 
 Compiling for Linux
 ===================
@@ -149,10 +167,32 @@
   On success, the resulting rpm(s) can usually be found under the proper
   "/usr/src/<rpmdir>/RPMS/<arch>" directory.
 
-Compiling for Windows
-=====================
+Compiling for Windows using CMake
+=================================
+The easiest way is to compile is to use vcpkg (https://github.com/Microsoft/vcpkg)
+to install libsndfile (required) and cppunit (optional). In the vcpkg install dir
+type:
+.\vcpkg.exe install libsndfile cppunit [--triplet x64-windows]
+
+This should install the libraries in vcpkg, add the triplet option if you wish to
+get the 64bit libraries.
+
+In an empty directory type:
+cmake <libgig source dir> -DCMAKE_TOOLCHAIN_FILE=<vcpkg dir>\scripts\buildsystems\vcpkg.cmake
+[-G"Visual Studio 15 2017 Win64"]
+
+Use the -G option to select the visual studio version and whether to compile for
+64bits.
+
+This will create libgig.sln file which you can open in visual studio or you can use
+the following command line to compile:
+
+cmake --build . --config <Release|Debug|MinRelSize|RelWithDebInfo>
+
+Compiling for Windows using Dev-C++
+===================================
 
-  libgig and its tools can be compiled for Windows using Bloodshed Dev-C++,
+  libgig and its tools can also be compiled on Windows using Bloodshed Dev-C++,
   which is a free (GPL) C++ integrated development environment for Windows.
   It is also possible to use MSYS from MinGW, which allows you to use
   './configure && make' like the linux builds.