cmake-conan VS FunctionalPlus

Some pure conan options, there's a 2.0 super early developer preview for https://github.com/conan-io/cmake-conan/tree/develop2

I totally agree with you. Have a look at the new cmake-conan integration using Dependency Provider in the develop2 branch : https://github.com/conan-io/cmake-conan/tree/develop2

Assuming you're using cmake as your build system, you can use conan.cmake which would allow you to run cmake normally.

I've always used conan together with the conan cmake module

If OP doesn't want to bother with the all the Conan pre-configuration commands and scripts, there's a really convenient script to embed everything Conan-related inside your CMakeLists, only asking for the path to conan.exe during CMake-configuration step: https://github.com/conan-io/cmake-conan

I always wanted to try to use cmake-conan so I could let Conan grab all packages but have a neat cmake script being in charge of what gets built when. Also, this would allow me to easily switch between CMake fetchcontent and Conan packages that may or may not be stashed automatically on a local Artifactory server. Secondly, since now all build requirements are stashed on a server and binary reproducible, you could concider adding icecream and ccache into the mix. (Try running a node one of your buildservers for massive speadups with icecream) This however does require a reproducible build environment (by configure script) which conan again is really good in.

If you want everything Conan-related to be silently managed by your CMake script, check this: https://github.com/conan-io/cmake-conan

cmake_minimum_required(VERSION 3.20) project(wxocto CXX) set(CMAKE_CXX_STANDARD 23) # Request the required wxWidgets libs find_package(wxWidgets 3.1 REQUIRED) # Include the wxWidgets use file to initialize various settings include(${wxWidgets_USE_FILE}) list(APPEND CMAKE_MODULE_PATH ${CMAKE_BINARY_DIR}) list(APPEND CMAKE_PREFIX_PATH ${CMAKE_BINARY_DIR}) #if(NOT EXISTS "${CMAKE_BINARY_DIR}/conan.cmake") # message(STATUS "Downloading conan.cmake from https://github.com/conan-io/cmake-conan") # file(DOWNLOAD "https://raw.githubusercontent.com/conan-io/cmake-conan/v0.16.1/conan.cmake" # "${CMAKE_BINARY_DIR}/conan.cmake" # EXPECTED_HASH SHA256=396e16d0f5eabdc6a14afddbcfff62a54a7ee75c6da23f32f7a31bc85db23484 # TLS_VERIFY OFF) #endif() include(./conan.cmake) conan_cmake_configure( REQUIRES easyhttpcpp/2.1.0 nlohmann_json/3.10.2 expat/2.4.1 GENERATORS cmake_find_package ) conan_cmake_autodetect(settings) if (WIN32 OR MINGW) set(target WIN32) set(options Poco:enable_netssl_win=True Poco:enable_netssl=False) endif () conan_cmake_install(PATH_OR_REFERENCE . BUILD missing REMOTE conancenter SETTINGS ${settings} OPTIONS ${options} PROFILE cross) find_package(expat) find_package(easyhttpcppeasyhttp) find_package(nlohmann_json) add_executable(wxocto ${target} main.cpp mainwindow/MainWindowBase.cpp mainwindow/MainWindowBase.h mainwindow/MainWindow.cpp mainwindow/MainWindow.h MainApp.cpp MainApp.h settings/wxOctoSettings.h settings/OctoPrintServerSettingsPage.cpp settings/OctoPrintServerSettingsPage.h settings/OctoPrintServerSettingsPagePanel.cpp settings/OctoPrintServerSettingsPagePanel.h helper.h octoprint/OctoprintFile.cpp octoprint/OctoprintFile.h octoprint/FetchFilesThread.cpp octoprint/FetchFilesThread.h octoprint/OctoprintJob.cpp octoprint/OctoprintJob.h octoprint/FetchPrintStatusThread.cpp octoprint/FetchPrintStatusThread.h octoprint/OctoApiEventIds.h octoprint/SelectAndPrintFileThread.cpp octoprint/SelectAndPrintFileThread.h octoprint/CancelPrintThread.cpp octoprint/CancelPrintThread.h octoprint/PausePrintThread.cpp octoprint/PausePrintThread.h octoprint/ResumePrintThread.cpp octoprint/ResumePrintThread.h octoprint/spoolmanager/FetchSpoolsThread.cpp octoprint/spoolmanager/FetchSpoolsThread.h octoprint/spoolmanager/OctoprintSpool.cpp octoprint/spoolmanager/OctoprintSpool.h octoprint/spoolmanager/OctoprintSpoolData.cpp octoprint/spoolmanager/OctoprintSpoolData.h spoolmanager/SpoolDialogBase.cpp spoolmanager/SpoolDialogBase.h spoolmanager/AddSpoolDialog.cpp spoolmanager/AddSpoolDialog.h spoolmanager/EditSpoolDialog.cpp spoolmanager/EditSpoolDialog.h) target_include_directories(wxocto PRIVATE ${wxWidgets_INCLUDE_DIRS}) target_link_libraries(wxocto expat::expat ${wxWidgets_LIBRARIES} easyhttpcppeasyhttp::easyhttpcppeasyhttp nlohmann_json::nlohmann_json)

Hoogle is really amazing!

Inspired by it, I implemented something similar for FunctionalPlus (a functional-programming library for C++): https://www.editgym.com/fplus-api-search/

I'd love to see more projects taking this path too. :)

A comparable library is FunctionalPlus

You can get a feel for it on its api search site: as an example, enter these queries:

I use a library called FunctionalPlus daily.

Any project CML file that is more complex than this is mismanaged and needs fixing asap. There is absolutely no reason to make CML files describing requirements of a library substantially more complex other than if you have a vendetta against yourself, package maintainers and your users.

FunctionalPlus - 30 lines for usage requirements + 60 for install rules: just simple commands creating a target, setting properties and defining install rules. Hmm, nothing unholy here.

You can copy this project structure: https://github.com/Dobiasd/FunctionalPlus