[kdbus] KDBUS_ITEM_PAYLOAD_OFF items are (once again) relative to msg header

[platform/upstream/glib.git] / README.win32

diff --git a/README.win32 b/README.win32
index a04417f..6e2d9da 100644 (file)
--- a/README.win32
+++ b/README.win32
@@ -67,6 +67,20 @@ you would be allowed by the license to distrubute a GLib linked to
 msvcr70.dll or msvcr80.dll, as those are not part of the operating\r
 system, but of the MSVC product. msvcrt.dll is part of Windows.\r
 \r
 msvcr70.dll or msvcr80.dll, as those are not part of the operating\r
 system, but of the MSVC product. msvcrt.dll is part of Windows.\r
 \r

+For people using Visual Studio 2005 or later:\r
+\r
+If you are building GLib-based libraries or applications, or GLib itself\r
+and you see a C4819 error (or warning, before C4819 is treated as an error\r
+in msvc_recommended_pragmas.h), please be advised that this error/warning should\r
+not be disregarded, as this likely means portions of the build is not being\r
+done correctly, as this is an issue of Visual Studio running on CJK (East Asian)\r
+locales.  This is an issue that also affects builds of other projects, such as\r
+QT, Firefox, LibreOffice/OpenOffice, Pango and GTK+, along with many other projects.\r
+\r
+To overcome this problem, please set your system's locale setting for non-Unicode to\r
+English (United States), reboot, and restart the build, and the code should build\r
+normally.  See also this GNOME Wiki page [1] that gives a bit further info on this.\r
+\r

 Building software that use GLib or GTK+\r
 =======================================\r
 \r
 Building software that use GLib or GTK+\r
 =======================================\r
 \r


@@ -159,11 +173,22 @@ and libtool documentation.
 Building with Visual Studio\r
 ===========================\r
 \r
 Building with Visual Studio\r
 ===========================\r
 \r

-In an unpacked tarball, you will find in build\win32\vs9 a solution\r
-file that can be used to build the GLib DLLs and some auxiliary\r
-programs. Read the README.txt file in that folder for more\r
-information. Note that you will need a libintl implementation, and\r
-zlib.\r
+A more detailed outline of building GLib with its dependencies can\r
+now be found on the GNOME wiki:\r
+\r
+https://wiki.gnome.org/Projects/GTK%2B/Win32/MSVCCompilationOfGTKStack\r
+\r
+Please do not build GLib in paths that contain spaces in them, as\r
+this may cause problems during compilation and during usage of the\r
+library.\r
+\r
+In an unpacked tarball, you will find in build\win32\vs9 (VS 2008) and\r
+build\win32\vs10 (VS 2010) a solution file that can be used to build\r
+the GLib DLLs and some auxiliary programs under VS 2008 and VS 2010\r
+(Express Edition will suffice with the needed dependencies) respectively.\r
+Read the README.txt file in those folders for more\r
+information. Note that you will need a libintl implementation, zlib, and \r
+libFFI.\r

 \r
 If you are building from a GIT checkout, you will first need to use some\r
 Unix-like environment or run build/win32/setup.py, \r
 \r
 If you are building from a GIT checkout, you will first need to use some\r
 Unix-like environment or run build/win32/setup.py, \r


@@ -356,3 +381,4 @@ dependencies order.
       +- plug-ins\r
           +- python\r
 \r
       +- plug-ins\r
           +- python\r
 \r

+[1]: https://wiki.gnome.org/Projects/GTK%2B/Win32/MSVCCompilationOfGTKStack under "Preparations"\r