1
0
Fork 0
mirror of https://github.com/warmcat/libwebsockets.git synced 2025-03-09 00:00:04 +01:00
libwebsockets/minimal-examples
Andy Green 67f532a8c6 cmake: bring tls include requirement out as PUBLIC
There's no problem for library build, also with LWS_WITH_MINIMAL_EXAMPLES,
but after install at least on OSX, there are problems finding the installed
lws include dir (concealed on most platforms by the path being in the
default search list for the toolchain), and the references in the lws
includes to the tls includes meaning that explicit paths for that must be
available at consuming cmakes.

This patch enhances the cmake config installed by lws to deal with adding
the lws include paths to CMAKE_REQUIRED_INCLUDES and include_directories,
so it can be found before the target is introduced.

The tls include is passed back up the CMakeLists layers and the lws targets
marked with target_include_directories(PUBLIC) with them, so they are
understood as needed by consumers.

More boilerplate is moved out of the example consuming cmakes.

After this, on machines with previous installs of older lws, you may have to
clean out the cmake install path, that is usually something like

/usr/local/lib/cmake/libwebsockets/*

before make installing lws and putting the latest content in there.
2021-10-28 08:12:48 +01:00
..
client cmake: bring tls include requirement out as PUBLIC 2021-10-28 08:12:48 +01:00
embedded minimal: ss: embedded: RT595S ACM transport 2021-10-24 16:50:39 +01:00
server/hello_world cmake: bring tls include requirement out as PUBLIC 2021-10-28 08:12:48 +01:00
ssproxy cmake: bring tls include requirement out as PUBLIC 2021-10-28 08:12:48 +01:00
CMakeLists.txt examples: move existing to m-e-lowlevel and start repoulating m-e with SS 2021-10-08 09:49:05 +01:00
README.md examples: move existing to m-e-lowlevel and start repoulating m-e with SS 2021-10-08 09:49:05 +01:00

minimal-examples

These are examples using the high-level Secure Streams features of lws.

There are lower-level examples in ./minimal-examples-lowlevel that cover more usecases. However the capability of Secure Streams is continuing to cover more cases and it is quite a bit simpler to use.