project_options
cmake-conan
Our great sponsors
project_options | cmake-conan | |
---|---|---|
2 | 18 | |
320 | 799 | |
- | 2.5% | |
8.5 | 8.0 | |
12 days ago | 26 days ago | |
CMake | Python | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
project_options
-
CMake+Conan2 project template example repositories?
I had been using the project_options repository to bootstrap most of my CMake repositories, but it appears like this is not able to handle Conan2 (due to the usage cmake-conan, on a pre-2.0-compatible version of that repo).
-
The pool of talented C++ developers is running dry
- flags like "-fsanitize=address,leak,undefined -fanalyzer -Wthread-safety -D_FORTIFY_SOURCE=" should be baked in to a default "dev"/"debug" mode newbies shouldn't need to know/think about
Did you try project_options[0]? I recommend it to all newbies like me. Just set the "enable_developer_mode=true" and you get all that stuff for free.
> - I have to Google what headers cstd/std stuff comes from half the time
In Clion you can cmd+click on the symbol and it leads to the header.
Another recommended resource is https://github.com/cpp-best-practices/
[0]: https://github.com/aminya/project_options
cmake-conan
-
Conan Unrecongnized commands error
-- The CXX compiler identification is GNU 9.4.0-- The C compiler identification is GNU 9.4.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Setting build type to 'RelWithDebInfo' as none was specified. -- /usr/local/bin/ccache found and enabled -- Downloading conan.cmake from https://github.com/conan-io/cmake-conan -- Conan: Adding cci remote repository (https://center.conan.io) verify ssl (True) usage: conan remote [-h] [-v [V]] {add,auth,disable,enable,list,list-users,login,logout,remove,rename,set-user,update} ... conan remote: error: unrecognized arguments: https://center.conan.io True ERROR: Exiting with code: 2 CMake Error at build/conan.cmake:858 (message): Conan remote failed='2' Call Stack (most recent call first): build/_deps/_project_options-src/src/Conan.cmake:20 (conan_add_remote) build/_deps/_project_options-src/src/Index.cmake:182 (run_conan) build/_deps/_project_options-src/src/DynamicProjectOptions.cmake:132 (project_options) CMakeLists.txt:79 (dynamic_project_options)-- Configuring incomplete, errors occurred! See also "/home/user/Desktop/bitwyre/trading/intermediaries/cram_cpp_v3/build/CMakeFiles/CMakeOutput.log".
-
CMake+Conan2 project template example repositories?
Some pure conan options, there's a 2.0 super early developer preview for https://github.com/conan-io/cmake-conan/tree/develop2
-
vcpkg vs conan
https://github.com/conan-io/cmake-conan/tree/develop2 might interest you :) we love feedback
-
Conan package manager completely broken after 2.0 release
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
-
Conan 2.0, the new version of the open-source C and C++ package manager
I've always used conan together with the conan cmake module
- Use cmake to install dependency libraries?
-
Debug Conan recipes in VS Code
using conan from within cmake you can use this https://github.com/conan-io/cmake-conan, or just write your own execute process way of calling it . https://cmake.org/cmake/help/latest/command/execute_process.html
- CMake + Poco + FetchContent build options problem
-
Where should I store a C++ header file that I want to use for multiple Visual Studio projects?
See https://github.com/conan-io/cmake-conan for a neat wrapper that I use in almost all my projects
-
Best way to manage dependencies with c++?
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.
What are some alternatives?
cmake-registry - A cmake modules registry based on vcpkg
CPM.cmake - 📦 CMake's missing package manager. A small CMake script for setup-free, cross-platform, reproducible dependency management.
void_switch - 3D printable magnetic separation contactless key switch and stabilizers (OpenSCAD files)
Raylib-Basic-Project
cupcake.cmake - CMake boilerplate for an opinionated project structure.
POCO - The POCO C++ Libraries are powerful cross-platform C++ libraries for building network- and internet-based applications that run on desktop, server, mobile, IoT, and embedded systems.
gui_starter_template - A template CMake project to get you started with C++ and tooling
conan - Conan - The open-source C and C++ package manager
cmake-init - The missing CMake project initializer
boost-cmake - Easy Boost integration in CMake projects
gz-cmake - A set of CMake modules that are used by the C++-based Gazebo projects.
hunter - CMake driven cross-platform package manager for C/C++.