Automatically created conanfile.txt shows different generators

I’m using the CMake wrapper by downloading the conan.cmake-file and I’m calling

conan_cmake_run(REQUIRES <PACKAGE>/<VERSION>
				BASIC_SETUP
				CMAKE_TARGETS
				GENERATORS cmake_find_package cmake_paths
				OPTIONS ${CONAN_OPTIONS}
				BUILD missing
)

This leads to the creation of several files in my output folder. The CMake output shows:

conanfile.txt: 
Generator cmake created conanbuildinfo.cmake

conanfile.txt: 
Generator txt created conanbuildinfo.txt

conanfile.txt: 
Generator cmake_paths created conan_paths.cmake

conanfile.txt: 
Generator cmake_find_package created Find<PACKAGE>.cmake

conanfile.txt: 
Generated conaninfo.txt

conanfile.txt: 
Generated graphinfo

In my output folder I find the conanfile.txt, which is “the recipe” created by the wrapper for my <PACKAGE>, I guess. Now when I open this file, I see the following:

[generators]
cmake

[requires]
<PACKAGE>/<VERSION>

[options]
...
some options
...

[imports]

I was wondering why [generators] is set to cmake and not cmake_find_package and cmake_paths?

[czoido]

Hi @akalali, Thanks for the feedback, that’s probably something we can do for future releases, anyway, if you want not to load the conanbuildinfo.cmake by default you can use the NO_LOAD argument in conan_cmake_run (it will be generated but not loaded).

[czoido]

I’m closing this as for the future we are moving in the direction of deprecating the use of conan_cmake_run and using separate calls to conan_cmake_configure, conan_cmake_autodetect and conan_cmake_install proposed here: https://github.com/conan-io/cmake-conan/pull/310. This is more explicit and can use latest Conan features because you can skip the auto-detection part if you want. Also, that way you can use just what you need without having nothing generated as default.