package variant without header files? about boost-cpp-feedstock HOT 6 CLOSED

congrats!!!! amazing work!

from boost-cpp-feedstock.

We should separate the package into multiple outputs. Then one should select the necessary parts of boost instead of all of it when building.

from boost-cpp-feedstock.

I guess the challenge is that listing the files that each split package is to include with conda requires manaully listing (or at least it did when i last looked at it).

It was impossible to say that everything in the include folder should go in one package.

That makes it really hard to maintain.

When i've needed to reduce the install size of my application, i simply removed the whole include directory in a post install script (along with all the .a files in the lib directory).

from boost-cpp-feedstock.

This change should be done in sync with:
https://github.com/AnacondaRecipes/boost-cpp-feedstock/tree/master/recipe

from boost-cpp-feedstock.

The way to do this would be to use install scripts for each component. These could install full directories at once. That said, there will also be libraries, docs, and possibly other things. So really what one would want to do is configure Boost to just install that component. Idk how well this strategy would work with Boost (maybe someone else here does), but that is something other split packages use successfully

from boost-cpp-feedstock.

This has been done in conda-forge/boost-feedstock#164, closing

from boost-cpp-feedstock.