James
James
Checking in https://github.com/conan-io/conan/pull/11828 if it could break some CI tests.
https://github.com/conan-io/conan/pull/11828 was merged, so this will be released in 1.52
Because those are not env-vars, those are CMake variables. No matter if you define them in the ``[env]`` (or ``[buildenv]``) section of the profile, it will be defined in the...
Because the compiler can be different in every computer. The ``-stdlib=libstdc++`` is constant, it is safe for Conan to add it. But clang can be ``clang`` in one computer, ``clang-12``...
This would be doable with the flexibility that ``CMakeToolchain``, but it needs to be explicit, for example we could define a ``conf`` like ``tools.cmake.cmaketoolchain:cxx_compiler``, that ``tools_requires`` packages could define, and...
Fixed in https://github.com/conan-io/conan/pull/11728, will be released in 2.0-beta.3
Hi @crystalsky Change it in the ``layout()`` method of the consuming ``conanfile.py`` https://docs.conan.io/en/latest/developing_packages/package_layout.html#package-layout
- Use a better identifier: ``conan_version`` - It is a comparable ``Version`` object Lets create a new issue for the ``traits`` args.
I don't think it is just a syntax issue, I see a problem with this, and is transitivity. For example, the generator that we are most likely using as default...
@czoido is going to propose some client side (from ``CMakeDeps``) configuration to customize how dependencies are consumed ("generated config.cmake", "generated Cmake Find module", "in-package cmake file").