3 Libwebsockets can be built using two different build systems
4 autoconf or CMake. autoconf only works on Unix systems, or mingw/cygwin
5 on Windows. CMake works differently and can generate platform specific
6 project files for most popular IDEs and build systems.
8 ################################### Autoconf ###################################
10 Building the library and test apps
11 ----------------------------------
13 You need to regenerate the autotools and libtoolize stuff for your system
20 ./configure --prefix=/usr --libdir=/usr/lib64 --enable-openssl
24 Christopher Baker reported that this is needed
25 (and I was told separately enabling openssl makes trouble somehow)
27 ./configure CC="gcc -arch i386 -arch x86_64" CXX="g++ -arch i386 -arch
28 x86_64" CPP="gcc -E" CXXCPP="g++ -E" --enable-nofork
32 I did the following to get working build, ping test is disabled when
35 1) install mingw64_w32 compiler packages from Fedora
36 2) additionally install mingw64-zlib package
37 3) ./configure --prefix=/usr --enable-mingw --host=x86_64-w64-mingw32
40 ------MIPS cross-build using OpenWRT
42 ./configure --prefix=/usr --without-extensions --host mips-openwrt-linux
44 I did not try building the extensions since they need cross-zlib, but it
45 should also be workable.
49 you may need --enable-builtin-getifaddrs if your toolchain
50 doesn't have it - openWRT uclibc has it so you don't need this option.
54 ./configure --prefix=/usr --host=arm-linux-gnueabi --without-client --without-extensions
56 you can build cross with client and extensions perfectly well, but
57 apart from the size shrink this has the nice characteristic that no
58 non-toolchain libraries are needed to build it.
61 otherwise if /usr/local/... and /usr/local/lib are OK then...
65 $ make && sudo make install
66 $ libwebsockets-test-server
68 should be enough to get a test server listening on port 7861.
71 Configure script options
72 ------------------------
74 There are several other possible configure options
76 --enable-openssl Builds in the SSL support
78 --with-cyassl Use cyassl instead of OpenSSL... you will need CyaSSL
79 to have been configured with --enable-opensslExtra
82 --enable-libcrypto by default libwebsockets uses its own
83 built-in md5 and sha-1 implementation for
84 simplicity. However the libcrypto ones
85 may be faster, and in a distro context it
86 may be highly desirable to use a common
87 library implementation for ease of security
88 upgrades. Give this configure option
89 to disable the built-in ones and force use
90 of the libcrypto (part of openssl) ones.
92 --with-client-cert-dir=dir tells the client ssl support where to
93 look for trust certificates to validate
94 the remote certificate against.
96 --enable-noping Don't try to build the ping test app
97 It needs some unixy environment that
98 may choke in other build contexts, this
99 lets you cleanly stop it being built
101 --enable-builtin-getifaddrs if your libc lacks getifaddrs, you can build an
102 implementation into the library. By default your libc
105 --without-testapps Just build the library not the test apps
107 --without-client Don't build the client part of the library nor the
108 test apps that need the client part. Useful to
109 minimize library footprint for embedded server-only
112 --without-server Don't build the server part of the library nor the
113 test apps that need the server part. Useful to
114 minimize library footprint for embedded client-only
117 --without-daemonize Don't build daemonize.c / lws_daemonize
119 --disable-debug Remove all debug logging below lwsl_notice in severity
120 from the code -- it's not just defeated from logging
121 but removed from compilation
123 --without-extensions Remove all code and data around protocol extensions.
124 This reduces the code footprint considerably but
125 you will lose extension features like compression.
126 However that may be irrelevant for embedded use and
127 the code / data size / speed improvements may be
130 --with-latency Builds the latency-tracking code into the library...
131 this slows your library down a bit but is very useful
132 to find the cause of unexpected latencies occurring
133 inside the library. See README.test-apps for more
137 Externally configurable important constants
138 -------------------------------------------
140 You can control these from configure by just setting them as commandline
141 args throgh CFLAGS, eg
143 ./configure CFLAGS="-DLWS_MAX_ZLIB_CONN_BUFFER=8192"
146 They all have reasonable defaults usable for all use-cases except resource-
147 constrained, so you only need to take care about them if you want to tune them
148 to the amount of memory available.
150 - LWS_MAX_HEADER_NAME_LENGTH default 64: max characters in an HTTP header
151 name that libwebsockets can cope with
153 - LWS_MAX_HEADER_LEN default 4096: largest HTTP header value string length
154 libwebsockets can cope with
156 - LWS_INITIAL_HDR_ALLOC default 256: amount of memory to allocate initially,
157 tradeoff between taking too much and needless realloc
159 - LWS_ADDITIONAL_HDR_ALLOC default 64: how much to additionally realloc if
160 the header value string keeps coming
162 - MAX_USER_RX_BUFFER default 4096: max amount of user rx data to buffer at a
163 time and pass to user callback LWS_CALLBACK_RECEIVE or
164 LWS_CALLBACK_CLIENT_RECEIVE. Large frames are passed to the user callback
165 in chunks of this size. Tradeoff between per-connection static memory
166 allocation and if you expect to deal with large frames, how much you can
167 see at once which can affect efficiency.
169 - LWS_MAX_PROTOCOLS default 10: largest amount of different protocols the
172 - LWS_MAX_EXTENSIONS_ACTIVE default 10: largest amount of extensions we can
173 choose to have active on one connection
175 - SPEC_LATEST_SUPPORTED default 13: only change if you want to remove support
176 for later protocol versions... unlikely
178 - AWAITING_TIMEOUT default 5: after this many seconds without a response, the
179 server will hang up on the client
181 - CIPHERS_LIST_STRING default "DEFAULT": SSL Cipher selection. It's advisable
182 to tweak the ciphers allowed to be negotiated on secure connections for
183 performance reasons, otherwise a slow algorithm may be selected by the two
184 endpoints and the server could expend most of its time just encrypting and
185 decrypting data, severely limiting the amount of messages it will be able to
186 handle per second. For example::
188 "RC4-MD5:RC4-SHA:AES128-SHA:AES256-SHA:HIGH:!DSS:!aNULL"
190 - SYSTEM_RANDOM_FILEPATH default "/dev/urandom": if your random device differs
193 - LWS_MAX_ZLIB_CONN_BUFFER maximum size a compression buffer is allowed to
194 grow to before closing the connection. Some limit is needed or any connecton
195 can exhaust all server memory by sending it 4G buffers full of zeros which the
196 server is expect to expand atomically. Default is 64KBytes.
198 - LWS_SOMAXCONN maximum number of pending connect requests the listening
199 socket can cope with. Default is SOMAXCONN. If you need to use synthetic
200 tests that just spam hundreds of connect requests at once without dropping
201 any, you can try messing with these as well as ulimit (see later)
202 (courtesy Edwin van der Oetelaar)
204 echo "2048 64512" > /proc/sys/net/ipv4/ip_local_port_range
205 echo "1" > /proc/sys/net/ipv4/tcp_tw_recycle
206 echo "1" > /proc/sys/net/ipv4/tcp_tw_reuse
207 echo "10" > /proc/sys/net/ipv4/tcp_fin_timeout
208 echo "65536" > /proc/sys/net/core/somaxconn
209 echo "65536" > /proc/sys/net/ipv4/tcp_max_syn_backlog
210 echo "262144" > /proc/sys/net/netfilter/nf_conntrack_max
216 Update at 35f332bb46464feb87eb
218 Embedded server-only configuration without extensions (ie, no compression
219 on websocket connections), but with full v13 websocket features and http
220 server, built on ARM Cortex-A9:
222 ./configure --without-client --without-extensions --disable-debug --enable-nofork --without-daemonize
224 .text .rodata .data .bss
227 Context Creation, 1024 fd limit[2]: 12288 (12 bytes per fd)
228 Per-connection [3]: 4400 bytes
231 This shows the impact of the major configuration with/without options at
232 13ba5bbc633ea962d46d using Ubuntu ARM on a PandaBoard ES.
234 These are accounting for static allocations from the library elf, there are
235 additional dynamic allocations via malloc
237 Static allocations, ARM9
238 .text .rodata .data .bss
239 All (no without) 35024 9940 336 4104
240 without client 25684 7144 336 4104
241 without client, exts 21652 6288 288 4104
242 without client, exts, debug[1] 19756 3768 288 4104
243 without server 30304 8160 336 4104
244 without server, exts 25382 7204 288 4104
245 without server, exts, debug[1] 23712 4256 288 4104
247 Dynamic allocations: ARM9 (32 bit)
249 Context Creation, 1024 fd limit[2] in ulimit: 12288 (12 bytes per fd)
250 Per-connection (excluding headers[3]): 8740
252 Dynamic allocations: x86_64 (64 bit)
254 Context Creation, 1024 fd limit[2] in ulimit: 16384 (16 bytes per fd)
255 Per-connection (excluding headers[3]): 9224
257 [1] --disable-debug only removes messages below lwsl_notice. Since that is
258 the default logging level the impact is not noticable, error, warn and notice
259 logs are all still there.
261 [2] 1024 fd per process is the default limit (set by ulimit) in at least Fedora
264 [3] known headers are retained via additional mallocs for the lifetime of the
268 #################################### CMake ####################################
270 CMake is a multi-platform build tool that can generate build files for many
271 different target platforms. See more info at http://www.cmake.org
273 CMake also allows/recommends you to do "out of source"-builds, that is,
274 the build files are separated from your sources, so there is no need to
275 create elaborate clean scripts to get a clean source tree, instead you
276 simply remove your build directory.
278 Libwebsockets has been tested to build successfully on the following platforms
279 with SSL support (both OpenSSL/CyaSSL):
282 - Linux (x86 and ARM)
286 Building the library and test apps
287 ----------------------------------
289 The project settings used by CMake to generate the platform specific build
290 files is called CMakeLists.txt. CMake then uses one of its "Generators" to
291 output a Visual Studio project or Make file for instance. To see a list of
292 the available generators for your platform, simply run the "cmake" command.
294 Note that by default OpenSSL will be linked, if you don't want SSL support
295 see below on how to toggle compile options.
300 1. Install CMake 2.6 or greater: http://cmake.org/cmake/resources/software.html
301 (Most Unix distributions comes with a packaged version also)
305 3. Generate the build files (default is Make files):
312 (NOTE: The build/ directory can have any name and be located anywhere
313 on your filesystem, and that the argument ".." given to cmake is simply
314 the source directory of libwebsockets containing the CMakeLists.txt project
315 file. All examples in this file assumes you use "..")
317 4. Finally you can build using the generated Makefile:
321 Building on Windows (Visual Studio)
322 -----------------------------------
323 1. Install CMake 2.6 or greater: http://cmake.org/cmake/resources/software.html
325 2. Install OpenSSL binaries. http://www.openssl.org/related/binaries.html
326 (Preferably in the default location to make it easier for CMake to find them)
328 3. Generate the Visual studio project by opening the Visual Studio cmd prompt:
333 cmake -G "Visual Studio 10" ..
335 (NOTE: There is also a cmake-gui available on Windows if you prefer that)
337 4. Now you should have a generated Visual Studio Solution in your
338 <path to src>/build directory, which can be used to build.
340 Setting compile options
341 -----------------------
343 To set compile time flags you can either use one of the CMake gui applications
344 or do it via command line.
348 To list avaialable options (ommit the H if you don't want the help text):
352 Then to set an option and build (for example turn off SSL support):
354 cmake -DWITH_SSL=0 ..
356 cmake -DWITH_SSL:BOOL=OFF ..
360 If you have a curses enabled build you simply type:
361 (not all packages include this, my debian install does not for example).
367 On windows CMake comes with a gui application:
368 Start -> Programs -> CMake -> CMake (cmake-gui)
370 CyaSSL replacement for OpenSSL
371 ------------------------------
372 CyaSSL is a lightweight SSL library targeted at embedded system:
373 http://www.yassl.com/yaSSL/Products-cyassl.html
375 It contains a OpenSSL compatability layer which makes it possible to pretty
376 much link to it instead of OpenSSL, giving a much smaller footprint.
378 NOTE: At the time of writing this the current release of CyaSSL contains a
379 crash bug due to some APIs libwebsocket uses. To be able to use this you will
380 need to use the current HEAD in their official repository:
381 https://github.com/cyassl/cyassl
383 NOTE: cyassl needs to be compiled using the --enable-opensslExtra flag for
386 Compiling libwebsockets with CyaSSL
387 -----------------------------------
390 -DCYASSL_INCLUDE_DIRS=/path/to/cyassl
391 -DCYASSL_LIB=/path/to/cyassl/cyassl.a ..
393 NOTE: On windows use the .lib file extension for CYASSL_LIB instead.
397 To enable cross compiling libwebsockets using CMake you need to create
398 a "Toolchain file" that you supply to CMake when generating your build files.
399 CMake will then use the cross compilers and build paths specified in this file
400 to look for dependencies and such.
402 Below is an example of how one of these files might look like:
405 # CMake Toolchain file for crosscompiling on ARM.
407 # This can be used when running cmake in the following way:
409 # cmake .. -DCMAKE_TOOLCHAIN_FILE=/path/to/this/file/TC_arm-linux-gcc.cmake
412 set(CROSS_PATH /path/to/cross_environment/uClibc)
414 # Target operating system name.
415 set(CMAKE_SYSTEM_NAME Linux)
417 # Name of C compiler.
418 set(CMAKE_C_COMPILER "${CROSS_PATH}/bin/arm-linux-uclibc-gcc")
419 set(CMAKE_CXX_COMPILER "${CROSS_PATH}/bin/arm-linux-uclibc-g++")
421 # Where to look for the target environment. (More paths can be added here)
422 set(CMAKE_FIND_ROOT_PATH "${CROSS_PATH}")
424 # Adjust the default behavior of the FIND_XXX() commands:
425 # search programs in the host environment only.
426 set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
428 # Search headers and libraries in the target environment only.
429 set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
430 set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
432 Additional information on cross compilation with CMake:
433 http://www.vtk.org/Wiki/CMake_Cross_Compiling