folly

👋 trying to build fizz with glog 0.7.0, but ran into some regression test failure as below: same failure seen for wangle as well. relates to https://github.com/Homebrew/homebrew-core/pull/163094

folly_create_monolithic_library() is called unconditionally in the top-level CMakeLists.txt. When folly is consumed via FetchContent / add_subdirectory, the granular component OBJECT libraries are already available as build targets. The monolithic libfolly.a may not be desired in some use cases e.g., downstream projects that link against the granular libs Request: add a CMake option (e.g. FOLLY_BUILD_MONOLITHIC, defaulting to ON) to skip the monolithic library assembly. When off, an INTERFACE target named folly could aggregate the component targets so downstream target_link_libraries(... folly) calls continue to work without change.

Greetings from @conan-io, We are trying to update recipe in Conan Center Index: https://github.com/conan-io/conan-center-index/pull/27995#issuecomment-3317452387 While testing, we found that trying to compile folly with C++17 throws several errors, among them: It seems is directly using C++20 features in their source files. So I guess at least C++20 is needed in order to compile the library. But is still safe to be used (as a dependency) from a C++17 context? Menaning that if this library (nowadays) is still think to be used from C++17. In the project README, it clearly says that it is a C++17 library https://github.com/facebook/folly/blob/main/README.md?plain=1#L13