1 Notes about building lws
2 ========================
5 @section cm Introduction to CMake
7 CMake is a multi-platform build tool that can generate build files for many
8 different target platforms. See more info at http://www.cmake.org
10 CMake also allows/recommends you to do "out of source"-builds, that is,
11 the build files are separated from your sources, so there is no need to
12 create elaborate clean scripts to get a clean source tree, instead you
13 simply remove your build directory.
15 Libwebsockets has been tested to build successfully on the following platforms
16 with SSL support (both OpenSSL/wolfSSL):
18 - Windows (Visual Studio)
25 @section build1 Building the library and test apps
27 The project settings used by CMake to generate the platform specific build
28 files is called [CMakeLists.txt](CMakeLists.txt). CMake then uses one of its "Generators" to
29 output a Visual Studio project or Make file for instance. To see a list of
30 the available generators for your platform, simply run the "cmake" command.
32 Note that by default OpenSSL will be linked, if you don't want SSL support
33 see below on how to toggle compile options.
36 @section bu Building on Unix:
38 1. Install CMake 2.8 or greater: http://cmake.org/cmake/resources/software.html
39 (Most Unix distributions comes with a packaged version also)
43 3. Generate the build files (default is Make files):
51 4. Finally you can build using the generated Makefile:
53 $ make && sudo make install
55 **NOTE**: The `build/`` directory can have any name and be located anywhere
56 on your filesystem, and that the argument `..` given to cmake is simply
57 the source directory of **libwebsockets** containing the [CMakeLists.txt](CMakeLists.txt)
58 project file. All examples in this file assumes you use ".."
61 A common option you may want to give is to set the install path, same
62 as --prefix= with autotools. It defaults to /usr/local.
63 You can do this by, eg
65 $ cmake -DCMAKE_INSTALL_PREFIX:PATH=/usr .
69 On machines that want libraries in lib64, you can also add the
70 following to the cmake line
76 If you are building against a non-distro OpenSSL (eg, in order to get
77 access to ALPN support only in newer OpenSSL versions) the nice way to
78 express that in one cmake command is eg,
80 $ cmake .. -DOPENSSL_ROOT_DIR=/usr/local/ssl \
81 -DCMAKE_INCLUDE_DIRECTORIES_PROJECT_BEFORE=/usr/local/ssl \
85 When you run the test apps using non-distro SSL, you have to force them
86 to use your libs, not the distro ones
88 $ LD_LIBRARY_PATH=/usr/local/ssl/lib libwebsockets-test-server --ssl
91 To get it to build on latest openssl (2016-04-10) it needed this approach
93 cmake .. -DLWS_WITH_HTTP2=1 -DLWS_OPENSSL_INCLUDE_DIRS=/usr/local/include/openssl -DLWS_OPENSSL_LIBRARIES="/usr/local/lib64/libssl.so;/usr/local/lib64/libcrypto.so"
97 To build with debug info and _DEBUG for lower priority debug messages
100 $ cmake .. -DCMAKE_BUILD_TYPE=DEBUG
104 To build on Solaris the linker needs to be informed to use lib socket
105 and libnsl, and only builds in 64bit mode.
108 $ cmake .. -DCMAKE_C_FLAGS=-m64 -DCMAKE_EXE_LINKER_FLAGS="-lsocket -lnsl"
111 4. Finally you can build using the generated Makefile:
117 @section cmq Quirk of cmake
119 When changing cmake options, for some reason the only way to get it to see the
120 changes sometimes is delete the contents of your build directory and do the
124 @section cmw Building on Windows (Visual Studio)
126 1. Install CMake 2.6 or greater: http://cmake.org/cmake/resources/software.html
128 2. Install OpenSSL binaries. http://www.openssl.org/related/binaries.html
130 (**NOTE**: Preferably in the default location to make it easier for CMake to find them)
133 Be sure that OPENSSL_CONF environment variable is defined and points at
134 <OpenSSL install location>\bin\openssl.cfg
136 3. Generate the Visual studio project by opening the Visual Studio cmd prompt:
142 cmake -G "Visual Studio 10" ..
145 (**NOTE**: There is also a cmake-gui available on Windows if you prefer that)
148 See this link to find out the version number corresponding to your Visual Studio edition:
149 http://superuser.com/a/194065
151 4. Now you should have a generated Visual Studio Solution in your
152 `<path to src>/build` directory, which can be used to build.
154 5. Some additional deps may be needed
160 6. If you're using libuv, you must make sure to compile libuv with the same multithread-dll / Mtd attributes as libwebsockets itself
163 @section cmwmgw Building on Windows (MinGW)
165 1. Install MinGW: http://sourceforge.net/projects/mingw/files
167 (**NOTE**: Preferably in the default location C:\MinGW)
169 2. Fix up MinGW headers
171 a) Add the following lines to C:\MinGW\include\winsock2.h:
173 #if(_WIN32_WINNT >= 0x0600)
175 typedef struct pollfd {
181 } WSAPOLLFD, *PWSAPOLLFD, FAR *LPWSAPOLLFD;
183 WINSOCK_API_LINKAGE int WSAAPI WSAPoll(LPWSAPOLLFD fdArray, ULONG fds, INT timeout);
185 #endif // (_WIN32_WINNT >= 0x0600)
187 b) Create C:\MinGW\include\mstcpip.h and copy and paste the content from following link into it:
189 http://wine-unstable.sourcearchive.com/documentation/1.1.32/mstcpip_8h-source.html
191 3. Install CMake 2.6 or greater: http://cmake.org/cmake/resources/software.html
193 4. Install OpenSSL binaries. http://www.openssl.org/related/binaries.html
195 (**NOTE**: Preferably in the default location to make it easier for CMake to find them)
198 Be sure that OPENSSL_CONF environment variable is defined and points at
199 <OpenSSL install location>\bin\openssl.cfg
201 5. Generate the build files (default is Make files) using MSYS shell:
203 $ cd /drive/path/to/src
206 $ cmake -G "MSYS Makefiles" -DCMAKE_INSTALL_PREFIX=C:/MinGW ..
208 (**NOTE**: The `build/`` directory can have any name and be located anywhere
209 on your filesystem, and that the argument `..` given to cmake is simply
210 the source directory of **libwebsockets** containing the [CMakeLists.txt](CMakeLists.txt)
211 project file. All examples in this file assumes you use "..")
214 To generate build files allowing to create libwebsockets binaries with debug information
215 set the CMAKE_BUILD_TYPE flag to DEBUG:
217 $ cmake -G "MSYS Makefiles" -DCMAKE_INSTALL_PREFIX=C:/MinGW -DCMAKE_BUILD_TYPE=DEBUG ..
219 6. Finally you can build using the generated Makefile and get the results deployed into your MinGW installation:
226 @section mbed3 Building on mbed3
228 MBED3 is a non-posix embedded OS targeted on Cortex M class chips.
230 https://www.mbed.com/
232 It's quite unlike any other Posixy platform since the OS is linked statically
233 in with lws to form one binary.
235 At the minute server-only is supported and due to bugs in mbed3 network support,
236 the port is of alpha quality. However it can serve the test html, favicon.ico
237 and logo png and may be able to make ws connections. The binary for that
238 including the OS, test app, lws and all the assets is only 117KB.
240 0) Today mbed3 only properly works on FRDM K64F $35 Freescale Dev Board with
241 1MB Flash, 256KB SRAM and Ethernet.
243 http://www.freescale.com/products/arm-processors/kinetis-cortex-m/k-series/k6x-ethernet-mcus/freescale-freedom-development-platform-for-kinetis-k64-k63-and-k24-mcus:FRDM-K64F
245 1) Get a working mbed3 environment with arm-none-eabi-cs toolchain
246 (available in Fedora, Ubuntu and other distros)
248 2) Confirm you can build things using yotta by following the getting started guide here
250 https://docs.mbed.com/docs/getting-started-mbed-os/en/latest/
254 git clone https://github.com/warmcat/lws-test-server
258 4) mkdir -p yotta_modules ; cd yotta_modules
260 5) git clone https://github.com/warmcat/libwebsockets ; mv libwebsockets websockets ; cd ..
262 6) yotta target frdm-k64f-gcc
268 @section cmco Setting compile options
271 To set compile time flags you can either use one of the CMake gui applications
272 or do it via the command line.
274 @subsection cmcocl Command line
276 To list available options (omit the H if you don't want the help text):
280 Then to set an option and build (for example turn off SSL support):
282 cmake -DLWS_WITH_SSL=0 ..
284 cmake -DLWS_WITH_SSL:BOOL=OFF ..
286 @subsection cmcoug Unix GUI
288 If you have a curses-enabled build you simply type:
289 (not all packages include this, my debian install does not for example).
293 @subsection cmcowg Windows GUI
295 On windows CMake comes with a gui application:
296 Start -> Programs -> CMake -> CMake (cmake-gui)
299 @section wolf wolfSSL/CyaSSL replacement for OpenSSL
301 wolfSSL/CyaSSL is a lightweight SSL library targeted at embedded systems:
302 https://www.wolfssl.com/wolfSSL/Products-wolfssl.html
304 It contains a OpenSSL compatibility layer which makes it possible to pretty
305 much link to it instead of OpenSSL, giving a much smaller footprint.
307 **NOTE**: wolfssl needs to be compiled using the `--enable-opensslextra` flag for
310 @section wolf1 Compiling libwebsockets with wolfSSL
313 cmake .. -DLWS_USE_WOLFSSL=1 \
314 -DLWS_WOLFSSL_INCLUDE_DIRS=/path/to/wolfssl \
315 -DLWS_WOLFSSL_LIBRARIES=/path/to/wolfssl/wolfssl.a ..
318 **NOTE**: On windows use the .lib file extension for `LWS_WOLFSSL_LIBRARIES` instead.
320 @section cya Compiling libwebsockets with CyaSSL
323 cmake .. -DLWS_USE_CYASSL=1 \
324 -DLWS_CYASSL_INCLUDE_DIRS=/path/to/cyassl \
325 -DLWS_CYASSL_LIBRARIES=/path/to/wolfssl/cyassl.a ..
328 **NOTE**: On windows use the .lib file extension for `LWS_CYASSL_LIBRARIES` instead.
331 @section extplugins Building plugins outside of lws itself
333 The directory ./plugin-standalone/ shows how easy it is to create plugins
334 outside of lws itself. First build lws itself with -DLWS_WITH_PLUGINS,
335 then use the same flow to build the standalone plugin
337 cd ./plugin-standalone
341 make && sudo make install
344 if you changed the default plugin directory when you built lws, you must
345 also give the same arguments to cmake here (eg,
346 ` -DCMAKE_INSTALL_PREFIX:PATH=/usr/something/else...` )
348 Otherwise if you run lwsws or libwebsockets-test-server-v2.0, it will now
349 find the additional plugin "libprotocol_example_standalone.so"
351 lwsts[21257]: Plugins:
352 lwsts[21257]: libprotocol_dumb_increment.so
353 lwsts[21257]: libprotocol_example_standalone.so
354 lwsts[21257]: libprotocol_lws_mirror.so
355 lwsts[21257]: libprotocol_lws_server_status.so
356 lwsts[21257]: libprotocol_lws_status.so
358 If you have multiple vhosts, you must enable plugins at the vhost
359 additionally, discovered plugins are not enabled automatically for security
360 reasons. You do this using info->pvo or for lwsws, in the JSON config.
363 @section http2rp Reproducing HTTP2.0 tests
365 You must have built and be running lws against a version of openssl that has
366 ALPN / NPN. Most distros still have older versions. You'll know it's right by
369 lwsts[4752]: Compiled with OpenSSL support
370 lwsts[4752]: Using SSL mode
371 lwsts[4752]: HTTP2 / ALPN enabled
375 For non-SSL HTTP2.0 upgrade
377 $ nghttp -nvasu http://localhost:7681/test.htm
379 For SSL / ALPN HTTP2.0 upgrade
381 $ nghttp -nvas https://localhost:7681/test.html
384 @section cross Cross compiling
386 To enable cross-compiling **libwebsockets** using CMake you need to create
387 a "Toolchain file" that you supply to CMake when generating your build files.
388 CMake will then use the cross compilers and build paths specified in this file
389 to look for dependencies and such.
391 **Libwebsockets** includes an example toolchain file [cross-arm-linux-gnueabihf.cmake](cross-arm-linux-gnueabihf.cmake)
392 you can use as a starting point.
394 The commandline to configure for cross with this would look like
396 $ cmake .. -DCMAKE_INSTALL_PREFIX:PATH=/usr \
397 -DCMAKE_TOOLCHAIN_FILE=../cross-arm-linux-gnueabihf.cmake \
398 -DWITHOUT_EXTENSIONS=1 -DWITH_SSL=0
400 The example shows how to build with no external cross lib dependencies, you
401 need to provide the cross libraries otherwise.
403 **NOTE**: start from an EMPTY build directory if you had a non-cross build in there
404 before the settings will be cached and your changes ignored.
406 Additional information on cross compilation with CMake:
407 http://www.vtk.org/Wiki/CMake_Cross_Compiling
409 @section mem Memory efficiency
411 Embedded server-only configuration without extensions (ie, no compression
412 on websocket connections), but with full v13 websocket features and http
413 server, built on ARM Cortex-A9:
415 Update at 8dac94d (2013-02-18)
417 $ ./configure --without-client --without-extensions --disable-debug --without-daemonize
419 Context Creation, 1024 fd limit[2]: 16720 (includes 12 bytes per fd)
420 Per-connection [3]: 72 bytes, +1328 during headers
422 .text .rodata .data .bss
425 This shows the impact of the major configuration with/without options at
426 13ba5bbc633ea962d46d using Ubuntu ARM on a PandaBoard ES.
428 These are accounting for static allocations from the library elf, there are
429 additional dynamic allocations via malloc. These are a bit old now but give
430 the right idea for relative "expense" of features.
432 Static allocations, ARM9
434 | | .text | .rodata | .data | .bss |
435 |--------------------------------|---------|---------|-------|------|
436 | All (no without) | 35024 | 9940 | 336 | 4104 |
437 | without client | 25684 | 7144 | 336 | 4104 |
438 | without client, exts | 21652 | 6288 | 288 | 4104 |
439 | without client, exts, debug[1] | 19756 | 3768 | 288 | 4104 |
440 | without server | 30304 | 8160 | 336 | 4104 |
441 | without server, exts | 25382 | 7204 | 288 | 4104 |
442 | without server, exts, debug[1] | 23712 | 4256 | 288 | 4104 |
444 [1] `--disable-debug` only removes messages below `lwsl_notice`. Since that is
445 the default logging level the impact is not noticeable, error, warn and notice
446 logs are all still there.
448 [2] `1024` fd per process is the default limit (set by ulimit) in at least Fedora
449 and Ubuntu. You can make significant savings tailoring this to actual expected
450 peak fds, ie, at a limit of `20`, context creation allocation reduces to `4432 +
453 [3] known header content is freed after connection establishment