Open KepptnKool opened 4 years ago
Hi @KepptnKool
It doesnt seem a bug, but that the docs is a bit outdated or not complete. It should say that they are not displayed, if the binaries are there. In this case, as Binary: Build
it will be displaying them. If Binary: Cache
, then they won't be displayed in conan info
.
I am moving this to the docs repo to improve that. Thanks for reporting!
Is there a way to disable showing the build dependencies with conan info? Maybe run it twice?
conan info poco/1.9.4@ --dry-build=never
That will define that we don't want to build things, so it will skip the build-requires.
Even if some things are commanded to be built, you can show the fields you want only:
conan info poco/1.9.4@ --dry-build -n=license
When executing conan info on a conanfile also the packages in the build requires section are displayed. This also applies to transitive build requirements.
The documentation states, that build requirements are ignored by conan info. Specifically it states this:
My expectation is that conan info ignores all build requirements.
Environment Details
Steps to reproduce
conanfilea.txt
conanfileb.py
Then execute the following:
Logs
Note that cmake_installer appears in both versions in the output. That means, that the build requirement from the conanfilea.txt as well as the trasntive build requirement from conanfileb.py are displayed.