James

Hi @darin-costello Thanks for your feedback. > When using CMakeToolchain.user_presets_path(...) and including the conan generated preset json in a CMakePresets, Conan seems to be generating dummy "conan-*" presets for the...

> Sorry, yeah I've been using Ninja single config. But have you specified it with ``-c tools.cmake.cmaketoolchain:generator=Ninja``? If you don't do that, Conan is unaware that you are using such...

Hi @darin-costello Any update about the ``-c tools.cmake.cmaketoolchain:generator=Ninja`` conf? please let us know, many thanks for your feedback!

Hi @darin-costello Any further comment or question here? Thanks!

I am closing this ticket as resolved, but please don't hesitate to create new tickets for any further question or issue. Thanks for your feedback.

Hi @drmacdon Thanks for your feedback > The CMake conan_provider.cmake approach as pointed out in https://github.com/conan-io/cmake-conan/issues/635 does not invoke conan until the first find_package(), but CMake processes it just after...

Thanks for your feedback. > In the conan_provider.cmake file, I modified it as follows: Please don't provide code as images, but as text (with triple-quotes + language you get syntax...

Also take into account that it is a cache variable. Make sure to wipe completely your CMake cache.

Hi @mgratzke Thanks for your feedback. This hasn't been prioritized yet, but we are already starting conversations to check what can be done in this regard with the relevant Artifactory...

Hi @Adnn Thanks for your question. Yes, that would be an issue. In the ``conan workspace install``, all the ``editable`` package in the super-build are assumed to be managed by...