Faild in compiling with conan #836

Activity

1. facontidavide

   added 2 commits that reference this issue on Feb 2, 2026

   Fix Windows build issues (#762, #869, #836)

   ...

   bee1985

   Fix Windows build issues (#762, #869, #836) (#1089)

   ...

   46fe516
2. facontidavide

   closed this as completedon Feb 2, 2026
3. facontidavide commented on Feb 2, 2026

   

   facontidavide

   on Feb 2, 2026

   Collaborator

   More actions

   The error you're seeing ('settings.compiler' value not defined) means your Conan 2 profile hasn't been configured yet. Conan needs to know which compiler, OS, and architecture you're using before it can resolve packages.

   To fix this, run:

   conan profile detect

   This auto-detects your compiler and creates a default profile. After that, retry the install:

   conan install . -s build_type=Release --build=missing

   A few additional tips:

   • Make sure you're using Conan 2.x (which you are — 2.4.1). The command syntax differs from Conan 1.x, so double-check any tutorial you're following matches Conan 2.
   • After conan install, use the CMake presets it generates:

     cmake --preset conan-release
     cmake --build --preset conan-release

   • If you're building on Windows with MSVC, PR Fix Windows build issues (#762, #869, #836) #1089 (now merged) added proper MSVC runtime propagation in conanfile.py, which prevents Debug/Release runtime mismatch errors. Make sure you're on the latest version of the library.
   • If you don't need Conan, you can also build with plain CMake using the vendored dependencies (the default):

     mkdir build && cmake -S . -B build && cmake --build build --parallel

   Closing this as the profile detection is a Conan setup step and the MSVC runtime issue has been addressed in #1089.
4. facontidavide

   added a commit that references this issue on Feb 2, 2026

   Add Debug build to Windows CI matrix

   ...

   a590e6a