Lines Matching +full:cmake +full:- +full:core

9 ---|---
15 The user code can select by `info->options` flags at runtime which event loop
24 new cmake option that decides how they are built if any are selected,
30 at runtime after seeing the `info->options` flags requested by the user code.
34 core library build doesn't import any of their headers (see below for exception).
37 itself depends on the libwebsockets core library.  This allows just the needed
41 or on Windows you want plugins at all.  CMake will detect these situations and
50 ---|---
51 glib|`libwebsockets-evlib_glib.so`
52 event|`libwebsockets-evlib_event.so`
53 uv|`libwebsockets-evlib_uv.so`
54 ev|`libwebsockets-evlib_ev.so`
59 Lws looks for them at runtime using the build-time-configured path.
64 packaging is put the expected libs and pkgconfig in `libwebsockets` or `libwebsockets-core`,
65 the latter is followed by the provided cmake, and produce an additional package per build
66 event library plugin, named, eg `libwebsockets-evlib_glib`, which has a dependency on
67 `libwebsockets[-core]`.
69 Applications that use the default event loop can directly require `libwebsockets[-core]`,
71 `libwebsockets-evlib_glib`, which will bring that in and the core lws pieces in one step.
78 The cmake helper config `LWS_WITH_DISTRO_RECOMMENDED` is adapted to build all the