Is it possible to build multiple packages from single conanfile.py? (cont.)

[michaelmaguire]

I see in #1957 @bc-lee already asked "Is it possible to build multiple packages from single conanfile.py?"

I hesitate to re-ask this question because I like the simplicity of one package per conanfile recipe, but I'm raising this question on behalf of others in my organization who have asked about it.

Previously @memsharded stated:

I am not sure what you are trying to achieve, but no, you cannot have more than one recipe (for 1 package), in one conanfile.py.
Just use a different conanfile.py for each package.

I think one desire for this feature is to mirror the debian dpkg concepts of Source vs Binary package:

https://www.debian.org/doc/debian-policy/ch-controlfields.html

A Source package's control file roughly corresponds to part of a conanfile recipe (specifically the build_depends, depends and name), while the (possibly multiple) Binary packages generated from a single control file allow consumers to chose to download and link against only the subsets they need.

I can see the advantages:

• consistent build of multiple packages based on on a single recipe
• ability for consumer to download only a subset

and the disadvantages:

• no simple 1-1 correspondence between conanfile and package

Is this a directly we'd ever want for Conan?

To help us debug your issue please explain:

• I've read the CONTRIBUTING guide.
• I've specified the Conan version, operating system version and any tool that can be relevant.
• I've explained the steps to reproduce the error or the motivation/use case of the question/suggestion.

[michaelmaguire]

Ah, I see there is still an open ticket about this issue:

#3106 "[feature] Generate multiple packages from single compilation"