1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
|
# Building Ice for C++ on Windows
This file describes how to build Ice for C++ from sources on Windows and how
to test the resulting build.
ZeroC provides [Ice binary distributions][1] for various platforms and
compilers, including Windows and Visual Studio, so building Ice from sources is
usually unnecessary.
## C++ Build Requirements
### Operating Systems and Compilers
Ice was extensively tested using the operating systems and compiler versions
listed on [supported platforms][2].
The build requires the [Ice Builder for Visual Studio][8]; you need version
4.3.6 or greater to build Ice.
### Third-Party Libraries
Ice has dependencies on a number of third-party libraries:
- [bzip][3] 1.0
- [expat][4] 2.1
- [LMDB][5] 0.9
- [mcpp][6] 2.7.2 (with patches)
You do not need to build these packages yourself, as ZeroC supplies
[NuGet][7] packages for all of these third-party dependencies.
The Ice build system for Windows downloads and installs the NuGet command-line
executable and these NuGet packages when you build Ice for C++. The third-party
packages are installed in the ``ice/cpp/msbuild/packages`` folder.
## Building Ice
Open a Visual Studio command prompt. For example, with Visual Studio 2015, you
can open one of:
- VS2015 x86 Native Tools Command Prompt
- VS2015 x64 Native Tools Command Prompt
Using the first Command Prompt produces `Win32` binaries by default, while
the second Command Promt produces `x64` binaries by default.
In the Command Prompt, change to the `cpp` subdirectory:
cd cpp
Now you're ready to build Ice:
msbuild msbuild\ice.proj
This builds the Ice for C++ SDK and the Ice for C++ test suite, with
Release binaries for the default platform.
Set the MSBuild `Configuration` property to `Debug` to build debug binaries
instead:
msbuild msbuild\ice.proj /p:Configuration=Debug
The `Configuration` property may be set to `Debug` or `Release`.
Set the MSBuild `Platform` property to `Win32` or `x64` to build binaries
for a specific platform, for example:
msbuild msbuild\ice.proj /p:Configuration=Debug /p:Platform=x64
You can also skip the build of the test suite with the `BuildDist` target:
msbuild msbuild\ice.proj /t:BuildDist /p:Platform=x64
To build the test suite using the NuGet binary distribution use:
msbuild msbuild\ice.proj /p:ICE_BIN_DIST=all
You can also sign the Ice binaries with Authenticode, by setting the following
environment variables:
- SIGN_CERTIFICATE to your Authenticode certificate
- SIGN_PASSWORD to the certificate password
## Building Ice for UWP
The steps are the same as for Building Ice for C++ above, except you must also
use a `UWP` target.
To build Ice for UWP:
msbuild msbuild\ice.proj /t:UWPBuild
To skip the building of the test suite:
msbuild msbuild\ice.proj /t:UWPBuildDist
To build the test suite using the NuGet binary distribution use:
msbuild msbuild\ice.proj /t:UWPBuild /p:ICE_BIN_DIST=all
## NuGet packages
You can create a NuGet package with the following command:
msbuild msbuild\ice.proj /t:NuGetPack /p:BuildAllConfigurations=yes
This creates `zeroc.ice.v100\zeroc.ice.v100.nupkg`,
`zeroc.ice.v120\zeroc.ice.v120.nupkg`, `zeroc.ice.v140\zeroc.ice.v140.nupkg` or
`zeroc.ice.v141\zeroc.ice.v141.nupkg`
depending on the compiler you are using.
To create UWP NuGet packages, use the `UWPNuGetPack` target instead:
msbuild msbuild\ice.proj /t:UWPNuGetPack /p:BuildAllConfigurations=yes
This creates: `zeroc.ice.uwp.v140\zeroc.ice.uwp.v140.nupkg`,
`zeroc.ice.uwp.v140.x64\zeroc.ice.uwp.v140.x64.nupkg` and
`zeroc.ice.uwp.v140.x86\zeroc.ice.uwp.v140.x86.nupkg` for Visual Studio 2015
builds or `zeroc.ice.uwp.v140\zeroc.ice.uwp.v140.nupkg`,
`zeroc.ice.uwp.v140.x64\zeroc.ice.uwp.v140.x64.nupkg` and
`zeroc.ice.uwp.v140.x86\zeroc.ice.uwp.v140.x86.nupkg` for Visual Studio 2017
builds.
## Running the Test Suite
Python is required to run the test suite. Additionally, the Glacier2 tests
require the Python module `passlib`, which you can install with the command:
pip install passlib
After a successful source build, you can run the tests as follows:
python allTests.py
For the C++11 mapping you need to use the `Cpp11-Debug` or `Cpp11-Release`
configuration:
python allTests.py --config Cpp11-Debug
If everything worked out, you should see lots of `ok` messages. In case of a
failure, the tests abort with `failed`.
## Running the Universal Windows Platform Test Suite
Python is required to run the test suite. Additionally, the Glacier2 tests
require the Python module `passlib`, which you can install with the command:
pip install passlib
The scripts also require Ice for Python, you can build Ice for Python from
[python](../python) folder of this source distribution or install the Python
module `zeroc-ice`, using the following command:
pip install zeroc-ice
You can run the testsuite from the console using python:
python allTests.py --uwp --controller-app --platform x64 --config Release
If everything worked out, you should see lots of `ok` messages. In case of a
failure, the tests abort with `failed`.
[1]: https://zeroc.com/distributions/ice
[2]: https://doc.zeroc.com/display/Rel/Supported+Platforms+for+Ice+3.7.0
[3]: http://bzip.org
[4]: https://libexpat.github.io
[5]: https://symas.com/lightning-memory-mapped-database/
[6]: https://github.com/zeroc-ice/mcpp
[7]: https://www.nuget.org
[8]: https://github.com/zeroc-ice/ice-builder-visualstudio
|
