Greetings!
This issue is a suggestion based on previous work with Boost stacktrace and Conan.io. When building Boost, some libraries may be optional or dependend on a system library, which may or may not build a sub-library on the same project.
As Conan, and as most users, has no control over what B2 will find in the system, in the end, if you only want the base library, it will produce all libraries anyway. For fine control, I sent the PR boostorg/stacktrace#202 some time ago to stacktrace, so we can manage which library will be produced from that module.
The Cobalt, not much longer ago, introduced Cobalt IO SSL, which requires OpenSSL installed in the system. That library will be automatically built once b2 finds OpenSSL available, so there is no way to control its build.
As OpenSSL is literally not used by most of the Boost modules, it would be nice to have an option to control cobalt_io_ssl as done for stacktrace. For instance, when building with a package manager, we usually have all dependencies listed, and adding a new dependency due to a second library in Cobalt may be too much for users. Still, if we have an expected environment, where we want minimal libraries, but if b2 finds OpenSSL, it will increase the library number and build time too.
I can propose a PR as well, but first I want to know your thoughts. Regards!
Greetings!
This issue is a suggestion based on previous work with Boost stacktrace and Conan.io. When building Boost, some libraries may be optional or dependend on a system library, which may or may not build a sub-library on the same project.
As Conan, and as most users, has no control over what B2 will find in the system, in the end, if you only want the base library, it will produce all libraries anyway. For fine control, I sent the PR boostorg/stacktrace#202 some time ago to stacktrace, so we can manage which library will be produced from that module.
The Cobalt, not much longer ago, introduced Cobalt IO SSL, which requires OpenSSL installed in the system. That library will be automatically built once b2 finds OpenSSL available, so there is no way to control its build.
As OpenSSL is literally not used by most of the Boost modules, it would be nice to have an option to control cobalt_io_ssl as done for stacktrace. For instance, when building with a package manager, we usually have all dependencies listed, and adding a new dependency due to a second library in Cobalt may be too much for users. Still, if we have an expected environment, where we want minimal libraries, but if b2 finds OpenSSL, it will increase the library number and build time too.
I can propose a PR as well, but first I want to know your thoughts. Regards!