You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every recipe should have a test_package folder (default name for Conan to run after conan create) (+info: [poc] Test other generators: run several tests in test_*/conanfile.py conan-center-index#8389). thinking Maybe it is already there.
If cpp_info contains .set_property, then (one of) the generators CMakeDeps, MSBuildDeps, PkgConfigDeps are expected (maybe depending on the property).
We can not adopt it now. We are "migrating" recipes on CCI, supporting both cpp_info.names and set_property at same recipe to be prepared for 2.0, however, new generators are not used yet. We could think about a warning message to consider refactoring the recipe to new generators support.
I'm proposing three hooks:
test_package
folder (default name for Conan to run afterconan create
) (+info: Test other generators: run several tests in test_*/conanfile.py conan-center-index#8389). 🤔 Maybe it is already there.cpp_info
contains.name
or.filename
, then (one of) the generatorscmake_find_package[_multi]
are expectedcpp_info
contains.set_property
, then (one of) the generatorsCMakeDeps
,MSBuildDeps
,PkgConfigDeps
are expected (maybe depending on the property).Not really sure about the last two entries, not sure if we want (so) many packages with several
test_xxxx
folders.The text was updated successfully, but these errors were encountered: