CMake configuration

[Zentropivity]

A CMake config would be nice. It would make integrating uWebsockets into some other projects easier.
cmake packages reference

[ghost]

The problem with "let's all gather around MY favorite build system"-mentalities is that it always fails to succeed because it only takes one good project to opt-out for the entire utopia to fall.

Let's take OpenSSL for one - one of the most popular libraries in the world. It does not use CMake.

So how come it still is used in pretty much every server project on earth?

MY favorite build system is Make and it has been a standard since the 1970s. You can always propose improvements to it, but this project is not going to take the route of depending on Python, Perl, Golang and the whole JVM and Nodejs, just to pass a few flags to a compiler.

[Maverobot]

cmake is not a build system. It generates configurations for build systems.

[Zentropivity]

WARNING This example seems to be broken so it is just a concept? or something like that...
I was getting compile time segmentation fault xD (it could be anything on my side, so this may still work for others... )

In case someone is wondering how you could integrate uWebSockets into your own project using cmake...
It really is no big deal.
Here is how I did it using OpenSSL:

• Add the repository as git submodule (for reference, let's say you added it in lib/uWebSockets)
  Don't forget to init and update uWebSockets' submodule uSockets
• Find uSockets' and uWebSockets' dependency packages in your CMakeLists file
  (I am not using other packages here,
  check uWebSockets' Makefile for examples)

find_package(Threads REQUIRED)
# Threads::Threads - Link to this
find_package(ZLIB REQUIRED)
# ZLIB_INCLUDE_DIRS - where to find zlib.h, etc.
# ZLIB_LIBRARIES - List of libraries when using zlib.
find_package(OpenSSL REQUIRED)
# OPENSSL_LIBRARIES - All OpenSSL libraries and their dependencies.
# OPENSSL_INCLUDE_DIR - The OpenSSL include directory.

• Make a CMakeLists.txt file in lib
  (not forgetting to add lib as subdirectory)
  In that file, you would add:

# Build Release on third-party libs
set(CMAKE_BUILD_TYPE Release)

# Set the standards required
set(CMAKE_CXX_STANDARD 17)
set(CMAKE_CXX_STANDARD_REQUIRED ON)
set(CMAKE_C_STANDARD 11)
set(CMAKE_C_STANDARD_REQUIRED ON)

set(USOCKETS_DIR uWebSockets/uSockets/src)
set(UWEBSOCKETS_DIR uWebSockets/src)

add_library(
  uSockets STATIC
  ${USOCKETS_DIR}/libusockets.h
  ${USOCKETS_DIR}/bsd.c
  ${USOCKETS_DIR}/context.c
  ${USOCKETS_DIR}/loop.c
  ${USOCKETS_DIR}/socket.c
  ${USOCKETS_DIR}/crypto/openssl.c
  ${USOCKETS_DIR}/crypto/sni_tree.cpp
  ${USOCKETS_DIR}/crypto/wolfssl.c
  ${USOCKETS_DIR}/eventing/epoll_kqueue.c
  ${USOCKETS_DIR}/eventing/gcd.c
  ${USOCKETS_DIR}/eventing/libuv.c
)
target_compile_definitions(uSockets PRIVATE LIBUS_USE_OPENSSL)
# Enabling link time optimization with -flto is important for performance
# since it is set as PUBLIC, any library or executable linking this one will use the flag when built
target_compile_options(uSockets PUBLIC -flto)
target_link_options(uSockets
  PRIVATE -lstdc++
  PUBLIC -flto
)
target_link_libraries(uSockets ${OPENSSL_LIBRARIES} ${ZLIB_LIBRARIES})
target_include_directories(uSockets PUBLIC ${USOCKETS_DIR} ${OPENSSL_INCLUDE_DIR} ${ZLIB_INCLUDE_DIRS})

add_library(
  uWebSockets
  ${UWEBSOCKETS_DIR}/App.h
  ${UWEBSOCKETS_DIR}/AsyncSocketData.h
  ${UWEBSOCKETS_DIR}/AsyncSocket.h
  ${UWEBSOCKETS_DIR}/BloomFilter.h
  ${UWEBSOCKETS_DIR}/HttpContextData.h
  ${UWEBSOCKETS_DIR}/HttpContext.h
  ${UWEBSOCKETS_DIR}/HttpParser.h
  ${UWEBSOCKETS_DIR}/HttpResponseData.h
  ${UWEBSOCKETS_DIR}/HttpResponse.h
  ${UWEBSOCKETS_DIR}/HttpRouter.h
  ${UWEBSOCKETS_DIR}/LoopData.h
  ${UWEBSOCKETS_DIR}/Loop.h
  ${UWEBSOCKETS_DIR}/MessageParser.h
  ${UWEBSOCKETS_DIR}/MoveOnlyFunction.h
  ${UWEBSOCKETS_DIR}/Multipart.h
  ${UWEBSOCKETS_DIR}/PerMessageDeflate.h
  ${UWEBSOCKETS_DIR}/ProxyParser.h
  ${UWEBSOCKETS_DIR}/QueryParser.h
  ${UWEBSOCKETS_DIR}/TopicTree.h
  ${UWEBSOCKETS_DIR}/Utilities.h
  ${UWEBSOCKETS_DIR}/WebSocketContextData.h
  ${UWEBSOCKETS_DIR}/WebSocketContext.h
  ${UWEBSOCKETS_DIR}/WebSocketData.h
  ${UWEBSOCKETS_DIR}/WebSocketExtensions.h
  ${UWEBSOCKETS_DIR}/WebSocket.h
  ${UWEBSOCKETS_DIR}/WebSocketHandshake.h
  ${UWEBSOCKETS_DIR}/WebSocketProtocol.h
)
set_target_properties(uWebSockets PROPERTIES LINKER_LANGUAGE CXX)
target_compile_features(uWebSockets PUBLIC cxx_std_17)
target_link_libraries(uWebSockets uSockets)
target_include_directories(uWebSockets PUBLIC ${UWEBSOCKETS_DIR})

• Then you can just use uWebSockets as a library

add_executable(my_project fun.cpp)
target_link_libraries(my_project uWebSockets)

That is it, you can include uWS in your fun.cpp just like in the examples.

BEWARE the file lists may change! Check the repositories you cloned.
(I don't think I will update them here.)

[ghost]

It takes literally less time just specifying the compiler flags directly to the compiler than what it takes installing CMake

[Zentropivity]

Correct me if I am wrong...
but as long as I add -flto -O3 to the compile flags, the performance should be good and I'd have a statically linked uWebSockets.
Right? I might be misunderstanding something here...

With that in place

Linking boringssl took a while but it can only be for the better, right? xD
That one only has to be built once anyways... (just like uWebSockets this way)

[Zentropivity]

The reason I am going with cmake in the first place is because uWebSockets is not the only library I am using.
And some other libraries (like bullet3) have support for being added to cmake projects easily.

[ghost]

The reason I am going with cmake in the first place is because uWebSockets is not the only library I am using.

Noboy in the world is assuming uWS is your only library. Of course you have other libraries - that's the whole point of NOT using CMake - because no matter how much you want to, CMake will never be used by ALL libraries in the world.

Any Unix system can easily work with ANY build system as long as the result is in /usr/lib and /usr/include. That's where you bind together different libraries, in the standard includepaths!

[Zentropivity]

I am not telling you to use cmake.
I merely provided an example to use your library in a cmake project since some people might look for it.
Thanks for the help with the compile flags. Sorry for bothering you. :D