Package debug libraries

[vegardkv]

I am not too familiar with conda-forge, but I just recently discovered this package and conda-installed it, and noticed that the debug libraries are not included. This is an issue at least on Windows, where it is not recommended - and may not even work - to combine the Boost release libraries with a debug build.

When building Boost, this is controlled by the "variant" option AFAIK, which can be set to either debug or release (or both).

After some searching I realize that this issue may also be relevant for the boost-cpp feedstock.

[jakirkham]

This came up before in PR ( #35 ). The conclusion was they should either be in a different package or a different variant of this package. The latter would be preferable from a maintenance perspective. Also whatever we use should work for other Windows debug libraries.

[vegardkv]

Right, I had not noticed the pull request. I see that there are indeed valid arguments for not including the debug build as well.

Thank you for the PR reference!

[jakirkham]

FWIW this is still a great idea that we should really revive (especially as the tooling has caught up a bit). Raised issue ( conda-forge/conda-forge.github.io#544 ) to discuss how we do split packages and generate things like debug builds as products.

[h-vetinari]

Moved this issue from the obsolete boost-cpp feedstock to here.