You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In src/CMakeLists.txt, the SEASTAR_HAVE_URING macro is never included in the target_compile_definitions for the seastar-module, and the URING::uring library is also never linked with target_link_libraries.
The text was updated successfully, but these errors were encountered:
…rom Kefu Chai
before this change, when building seastar-module, we don't check for
the enabled features. so, for instance io uring backend is not enabled
even `Seastar_IO_URING` is set.
in this series we
* move `add_subdirectory(src)` down
* `#include` the used header files
* check for the enabled options,
* link against the related libraries, and
* add the required macro definitions
this should enable seastar-module to build with, for instance, io_uring
backend enabled. as `SEASTAR_HAVE_URING` enables this backend when
building `src/core/reactor_backend.cc`.
Fixes#2249Closes#2252
* github.com:scylladb/seastar:
build: support enabled options when building seastar-module
treewide: include required header files
build: move add_subdirectory(src) down
I understand that the modules support is still experimental. I also noticed that some components are not yet exported within the Seastar module, like the WebSocket server, for example.
So I just switched back to including the required headers in the meantime.
In src/CMakeLists.txt, the
SEASTAR_HAVE_URING
macro is never included in thetarget_compile_definitions
for theseastar-module
, and theURING::uring
library is also never linked withtarget_link_libraries
.The text was updated successfully, but these errors were encountered: