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
{{ message }}
Repository navigation
Commit f915183
Browse filesBrowse the repository at this point in the historyBrowse files
build: consume an existing httplib target instead of fetching a second copy
When a consumer has already defined `httplib::httplib`, fastmcpp_core now links
it rather than populating its own cpp-httplib checkout and exposing it as a
PUBLIC include directory. A binary that also links the consumer's copy was
compiling two versions of the same header-only library with different feature
macros, so `httplib::ClientImpl` had two layouts under one name -- an ODR
violation that presented as a crash inside the client, not a link error.
FASTMCPP_ENABLE_OPENSSL no longer stamps CPPHTTPLIB_OPENSSL_SUPPORT over an
externally supplied target, whose feature set is the consumer's to decide.
Standalone builds are unchanged: with no such target present, fastmcpp fetches
cpp-httplib as before.
Also adds FASTMCPP_BUILD_CLI (default ON) so an embedding project can skip the
command-line executable it does not ship.
0 commit comments