blob: bd7869c21794fd0fc65b1f1c1cf859451839c550 (
plain) (
blame)
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
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
|
# Zen Storage Service (zenserver)
This is the implementation of the local storage service for UE5. It is intended to be deployed on
user machines either as a daemon or launched ad hoc as required during of editor/cooker/game startup
Zen is currently EXPERIMENTAL and not intended to be used in production. We will make breaking changes to storage and application interfaces as well as significant performance improvements in the upcoming months to make it ready for general adoption.
Zen can also be deployed as a shared instance for use as a shared cache. It also supports upstream
connectivity to cloud storage services as well as other Zen server instances.
All platforms require [xmake](https://xmake.io)
Download the latest release [here](https://github.com/xmake-io/xmake/releases)
## Building on Windows
### Windows Setup
To build the code you will need Visual Studio 2022 (we use c++20 features), git and vcpkg.
* Install Visual Studio 2022
* Install [git](https://git-scm.com/download/win)
We use vcpkg to manage some libraries. Right now it's not set up on a project local
basis and requires manual bootstrap so you will need to do the following at least once:
* open up a command line window
* create a `git`/`github` directory somewhere for you to clone repos into
* issue `git clone https://github.com/microsoft/vcpkg.git` and build it using the `bootstrap-vcpkg.bat` script
* optional: add the `vcpkg` directory you cloned to your PATH to allow invoking vcpkg on the command line
* issue `vcpkg integrate install` to make sure you can build from Visual Studio using package manifests
Now you are ready to start building!
### Building with Visual Studio
We currently require Visual Studio 2022 or later.
* clone the `zen` repository if you haven't already
* run `git clone https://github.com/EpicGames/zen.git`
* run `xmake project -k vsxmake2022 -a x64 -y`
* open the `vsxmake2022\zen.sln` VS solution
* Note: if you want full connectivity with the http.sys server implementation you currently need to run
Visual Studio in ADMIN mode since http.sys requires elevation to be able to listen on a non-local network socket.
You can start Visual Studio in admin mode by holding CTRL-SHIFT when launching Visual Studio. Alternatively
you can add an URL reservation (see below)
* you can now build and run `zenserver` as usual from Visual Studio
* third-party dependencies will be built the first time via the `vcpkg` integration. This is not as
fast as it could be (it does not go wide) but should only happen on the first build and will leverage
a local build cache.
### Building with xmake
* configure xmake `xmake config -m debug|release -a x64`
* build zenserver `xmake build zenserver`
Binaries are located in the `build` directory
## Building on Linux
The following instructions have been collated using Ubuntu 20.04.
Zen makes heavy use of C++20 features which at the time of writing has limited
toolchain and C++ library support. A minimum compiler version of GCC-11 or
Clang-12 is required, along with GNU's libstdc+++-11 or newer. Note that it is
not currently possible to use anything other than the system's default C++
library (e.g. LLVM's libc++) due to the way that Zen's third party dependencies
are managed via `vcpkg`.
The first step is to acquire a suitable compiler and C++ library. On Ubuntu 20.04
GCC-11 is not available in the standard package repositories so Ubuntu's tool-
chain test respository needs to be added to Apt (note that this is _not required_
for Ubuntu 21.04 onwards);
```
sudo add-apt-repository -y ppa:ubuntu-toolchain-r/test
```
Now GCC-11 can be installed via Apt. This will also install a suitable version of
the C++ library.
```
sudo apt install -y --no-install-recommends g++-11
g++-11 --version
```
The easiest way to tell `xmake` to use the correct compiler version is to set
the `CXX` environment variable.
```
export CXX=g++-11
```
Next we need the `xmake` build system. For this we will download and install
`xmake` as a `.deb` package. Check the project's release page for more up to
date `.deb` files.
```
wget https://github.com/xmake-io/xmake/releases/download/v2.6.4/xmake-v2.6.4.amd64.deb
sudo dpkg -i xmake-v2.6.4.amd64.deb
xmake --version
```
To build some of the packages from vcpkg you may need some additional tools.
```
sudo apt-get install build-essential
```
Some of the dependencies in `vckpg` needs `pkg-config` so make sure to install that as well.
```
sudo apt-get install pkg-config
```
Some of Zen's third party dependencies are provided by Microsoft's `vcpkg`
C++ library manager. After cloning the project there is an initialisation step.
```
git clone https://github.com/microsoft/vcpkg.git ~/zen/vcpkg
~/zen/vcpkg/bootstrap-vcpkg.sh
~/zen/vcpkg/vcpkg --version
```
`xmake` uses an environment variable to find `vcpkg`. Alternatively this can be
done by including `VCPKG_ROOT=...` on the command line when invoking `xmake`.
```
export VCPKG_ROOT=~/zen/vcpkg
```
Clone the Zen project and tell `xmake` to use the correct GCC version.
```
git clone https://github.com/EpicGames/zen.git ~/zen/main
cd ~/zen/main
```
Now we are ready to build Zen. The `-y` skips `xmake` from prompting about
updating `vcpkg` packages.
```
xmake config -y --mode=debug
xmake build
```
Note that the command above to set the build variant to debug is optional. Tests
are only built in debug.The `xmake` flags `-vD` can be useful to diagnose
`xmake` issues.
### Distribution compatibility
Builds for Linux have a dependency on a modern version of the C++ library that
supports Zen's use of C++20 and the GCC-11 toolchain used (assuming the above
build instructions are adhered to). However there is no guarantee that the this
dependency is met when building on one Linux install and running on another. For
example, at the time of writing the LTS version of Ubuntu and Debian do not have
GCC-11's version of libstdc++.so.6 available in their package repositories.
To solve this, `xmake bundle` will bundle the required C++ .so and zenserver
binary together using AppImage. This can briefly be summarised as create a
squashfs file system containing zenserver and any C++ shared objects list with
`lld`. This file system is then concatenated with AppImage's runtime. This is
implemented in `scripts/bundle_linux.sh`. More details can be found here;
https://github.com/AppImage/AppImageKit
## Building on Mac
Building on Mac is very similar to Linux; install xmake, clone vcpkg and Zen and
then build the project.
```
## vcpkg
git clone https://github.com/microsoft/vcpkg.git ~/zen/vcpkg
~/zen/vcpkg/bootstrap-vcpkg.sh
~/zen/vcpkg/vcpkg --version
## xmake
curl -L https://github.com/xmake-io/xmake/releases/download/v2.6.2/xmake-v2.6.2.macosx.pkg > xmake-v2.6.2.macosx.pkg
sudo installer -pkg xmake-v2.6.2.macosx.pkg -target /
## Zen
git clone https://github.com/EpicGames/zen.git ~/zen/main
cd ~/zen/main
## Build
export VCPKG_ROOT=~/zen/vcpkg
xmake config -y --mode=debug --arch=x86_64
xmake build
```
# Implementation Notes
* The implementation currently depends only on a few libraries including the C++ standard library
* It uses exceptions for errors
* It is currently not portable as it uses Windows APIs directly. But as we all know, there is no
portable code, just code that has been ported many times. The plan is to implement support for
MacOS and Linux soon, and some research to enable it has been done
* `zenservice.exe` currently requires elevated access to enable `http.sys` access. This will be relaxed
in the future by offering to use a portable server interface without elevation
* The service endpoints are currently open on all NICs and will respond to requests from any host. This
will be tightened up in the future to require some degree of authentication to satisfy security
requirements
# Contributing Code
See [CODING.md](CODING.md)
# Debugging
When debugging multi-process scenarios such as when running `zenserver-test`, the [Microsoft Child Process Debugging Power Tool](https://marketplace.visualstudio.com/items?itemName=vsdbgplat.MicrosoftChildProcessDebuggingPowerTool)
is incredibly handy. When that is installed you may enable auto-attach to child processes via the Debug -> Other Debug Targets menu in Visual Studio.
# Testing
* There are some test projects
* `zencore-test` exercises unit tests in the zencore project
* `zenserver-test` exercises the zen server itself (functional tests)
The tests are implemented using [doctest](https://github.com/onqtam/doctest), which is similar to Catch in usage. We now also support [catch2](https://github.com/catchorg/Catch2)
# Adding a http.sys URL reservation (Windows only)
Registering a handler for an HTTP endpoint requires either process elevation (i.e running Zen as admin) or a one-time URL reservation. An URL reservation can be added by issuing a command like
`netsh http add urlacl url=http://*:1337/ user=stefan.boberg` (enable for a specific user)
or
`netsh http add urlacl url=http://*:1337/ sddl=D:(A;;GX;;;S-1-1-0)` (enable for any authenticated user)
|