[question] Package links against all dependent components instead of one

I’m trying to link against a specific Qt5 component qtCore for example. But for some reason conan links against all components that Qt declares. As a result I end up with a include list in a .vcxproj file That contains all components that Qt has.

… ….......conan\f2d3ec\1\include\QtWebEngine ….......conan\f2d3ec\1\include\QtWebEngineWidgets ….......conan\f2d3ec\1\include\QtPrintSupport ….......conan\f2d3ec\1\include\QtWebEngineCore ….......conan\f2d3ec\1\include\QtPositioning ….......conan\f2d3ec\1\include\QtWebChannel …

class LinkAgainstQtCoreOnly(ConanFile):
    def requirements(self):
        self.requires("qt/5.12.4")

    def package_info(self):
        self.cpp_info.requires = ['qtCore']

The docs say below code snippet would work:

class Library(ConanFile):
    name = 'library'
    requires = "openssl/1.0.2u"

    def package_info(self):
        self.cpp_info.requires = ['openssl::ssl']

In the previous example, the ‘library’ package and transitively all its consumers will link only with the component ssl from the openssl package.

• I’ve read the CONTRIBUTING guide.

[memsharded]

In any case, @gmikhaile if you are interested in this integration and want to try to contribute it, it would be very welcome. The fact that we don’t have enough time for it doesnt mean that it cannot be done.

[memsharded]

Hi @gmikhaile

yes, this is totally expected. The qmake integration is not multi-component yet. In fact, this integration still has not been modernized to be ready to be ported to Conan 2.0 (that is, to move it to the from conan.tools.qt package). Sometimes this modernization includes the multi-component support, if there is enough demand for it (so far only CMakeDeps and PkgConfigDeps got it), which doesn’t seem the case yet for QMake.