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
It would be great detailing what could be accessed via cpp_info, when having a component. For instance:
The package A has cpp_info.components["foo"].bindirs = ["lib/foo"].
Will this bindir be available via cpp_info.bindirs (the global one)?
When consuming package A, its cpp_info.bindirs will be available when using VirtualBuildEnv or VirtualRunEnv when not declaring A::foo in my cpp_info requires?
When reading the cpp_info page in Conan docs (https://docs.conan.io/2.0/reference/conanfile/methods/package_info.html) we can find explanation about cpp_info attributes and about components, but not about the transitive between them.
It would be great detailing what could be accessed via cpp_info, when having a component. For instance:
The package A has
cpp_info.components["foo"].bindirs = ["lib/foo"]
.cpp_info.bindirs
(the global one)?cpp_info.bindirs
will be available when usingVirtualBuildEnv
orVirtualRunEnv
when not declaringA::foo
in my cpp_info requires?/cc @garethsb
The text was updated successfully, but these errors were encountered: