1
Please refer to the following GNOME Live! page for more detailed
2
instructions on building JSON-GLib and its dependencies with Visual C++:
4
https://live.gnome.org/GTK%2B/Win32/MSVCCompilationOfGTKStack
6
This VS10 solution and the projects it includes are intended to be used
7
in a JSON-GLib source tree unpacked from a tarball. In a git checkout you
8
first need to use some Unix-like environment or manual work to expand
9
the .in files needed, mainly config.h.win32.in into config.h.win32.
10
You will also need to expand json-glib.vcxprojin and json-glib.vcxproj.filtersin
11
here into json-glib.vcxproj and json-glib.vcxproj.filters repectively.
13
The dependencies for this package are gettext-runtime (libintl), GLib*,
16
For the Dependencies, you may either:
18
a) look for all of the dependencies (except GLib*) under
20
http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32-bit) -OR-
21
http://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64-bit)
23
Please use the latest versions of these libraries that are available there,
24
these are packaged by Tor Lillqvist, which are built with MinGW/GCC.
25
Please see b) below regarding the build of GLib*
29
b) Build them yourself with VS10 (but you may most probably wish to get
30
gettext-runtime from the URL(s) mentioned in a)). Use the latest
31
stable versions for them (you may need to get the latest unstable version of
32
GLib if you are using an unstable version of JSON-GLib):
34
GLib*: Grab the latest sources from http://www.gtk.org under "Download"
35
(stable only-please make a search for the latest unstable versions)
36
ZLib: http://www.zlib.net
38
The above 2 packages all have supported mechanisms (Makefiles and/or Project
39
Files) for building under VS10 (upgrade the Project Files from earlier VS
40
versions will do for these, when applicable). It is recommended that ZLib
41
is built using the win32/Makefile.msc makefile with VS10 with the ASM routines
42
to avoid linking problems (copy zdll.lib to zlib1.lib[Release] or to zlib1d.lib
43
[Debug] after completion of compilation)-see win32/Makefile.msc in ZLib for
46
* This GLib refers to a build that is built by VS10
48
Set up the source tree as follows under some arbitrary top
51
<root>\json-glib\<this-json-glib-source-tree>
52
<root>\vs10\<PlatformName>
54
*this* file you are now reading is thus located at
55
<root>\json-glib\<this-json-glib-source-tree>\build\win32\vs10\README.
57
<PlatformName> is either Win32 or x64, as in the VS10 project files.
59
You should unpack the <dependent-package>-dev and <dependent-packge> (runtime)
60
into <root>\vs10\<PlatformName>, if you download any of the packages from
62
http://ftp.gnome.org/pub/GNOME/binaries/win32/dependencies/ (32-bit) -OR-
63
http://ftp.gnome.org/pub/GNOME/binaries/win64/dependencies/ (64-bit)
65
so that for instance libintl.h end up at
66
<root>\vs10\<PlatformName>\include\libintl.h.
68
If you build any of the dependencies yourselves, copy the:
69
-DLLs and EXEs into <root>\vs10\<PlatformName>\bin
70
-headers into <root>\vs10\<PlatformName>\include\
71
-LIBs into <root>\vs10\<PlatformName>\lib
73
If you have not built GLib with VS10 and placed the LIBs and headers in a
74
place where VS10 can find them automatically, you should also uncompress
75
your GLib sources in <root>\ and build it from there, following the
76
instructions in <root>\glib<-version>\build\win32\vs10, so that the required
77
headers, EXEs, DLLs and LIBs will end up in
78
<root>\vs10\<PlatformName>\include\glib-2.0 (headers)
79
<root>\vs10\<PlatformName>\lib (LIBs, also glib-2.0/include/glibconfig.h)
80
<root>\vs10\<PlatformName>\bin (EXEs/DLLs)
83
After the build of JSON-GLib, the "install" project will copy build results
84
and headers into their appropriate location under <root>\vs10\<PlatformName>.
85
For instance, built DLLs go into <root>\vs10\<PlatformName>\bin, built LIBs into
86
<root>\vs10\<PlatformName>\lib and JSON-GLib headers into
87
<root>\vs10\<PlatformName>\include\json-glib-1.0. This is then from where
88
project files higher in the stack are supposed to look for them, not
89
from a specific JSON-GLib source tree.
91
--Chun-wei Fan <fanc999@yahoo.com.tw>
92
--(adapted from the GLib VS9 README.txt file originally written by Tor Lillqvist)
added
removed
build/win32/vs10/README.txt
