cmake-conan VS ccache

-- 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".

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

https://github.com/conan-io/cmake-conan/tree/develop2 might interest you :) we love feedback

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

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

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

See https://github.com/conan-io/cmake-conan for a neat wrapper that I use in almost all my projects

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.

# Download and install ccache for faster compilation wget https://github.com/ccache/ccache/releases/download/v4.8.3/ccache-4.8.3.tar.xz tar -xf ccache-4.8.3.tar.xz pushd ccache-4.8.3 cmake . make -j $CPUS make install popd # Install NumPy, a dependency for PyTorch dnf install -y numpy # Install Python typing extensions for better type-checking sudo -u ec2-user pip3 install typing-extensions # Clone PyTorch repository and install from source git clone --recursive https://github.com/pytorch/pytorch.git pushd pytorch python3 setup.py install popd # Refresh the dynamic linker run-time bindings ldconfig # Install additional Python libraries for PyTorch sudo -u ec2-user pip3 install sympy filelock fsspec networkx

> What can I use to cache with MSVC that isn't Incredibuild?

Ccache works, but if you use the Visual Studio C++ compiler you need to configure your build to be cacheable.

https://github.com/ccache/ccache/wiki/MS-Visual-Studio

That ecosystem now is too young. All these things must be configured by an automatic installer. Packages and pods need to be tested before release, etc. Previous was 80 min compilation time of the Firestore package. Solved with https://ccache.dev/. But why Dart developers must know, how to install and configure object cache for C++ compilers?

Related

https://github.com/icecc/icecream - another option that does what distcc does, but aimed at a somewhat different use case.

https://ccache.dev/ - a similar idea but provides caching of build outputs instead of distributing builds. You can use it together with distcc to achieve even better performance.

> All those big changes introduce commits that make git bisect generally slower.

Bisection search is log2(n) so doubling the number of commits should only add one more bisection step, yes?

> Which might be awful if you also have some C code to recompile at every step of bisecting.

That reminds me, I've got to try out ccache (https://ccache.dev/ ) for my project. My full compile is one minute, but the three files that take longest to compiler rarely change.

I worked with the internals of this some 16 years ago, maintaining a customized version at Zeugma Systems. Some change of mine was reworked by someone and upstreamed:

https://github.com/ccache/ccache/commit/e8354384f67bc733bea5...