Ted Ralphs

For C extensions, wheels still don't seem to be a very good solution on Linux and OS X, but maybe they would work fine for packaging a statically linked binary....

I'm not sure exactly what's going on here, but `Osi_getNumCols` is from `libOsi`, which is provided by [coin-or-osi](https://github.com/conda-forge/coin-or-osi-feedstock), a dependency of `coin-or-cbc`.

I guess this needs the same setup and dependencies as CyLP. https://github.com/conda-forge/staged-recipes/pull/14950/files#diff-b0fbfb7ebff04033964e26d65718c744706d346658f63997fbb3c56eafa5a3c0R16-R31

I'm having trouble following what this package is trying to do. If you `conda install coin-or-cbc`, then `pip install cylp` should work out of the box. What is the advantage...

> Hey @tkralphs, thanks for stopping by! Generally, mixing conda & pip is discouraged, so one definite advantage would be being able to install cylp completely without pip! Another benefit...

Hey @h-vetinari, yes, I understand that the effort of actually doing the packaging is not automagic, what I meant was that the build itself should be. Looking at your build...

Yes, everything seems to get installed properly...

I spent some time trying to build this locally, but `conda` is a mysterious beast. Even when creating a clean environment with only `conda-build`, I get tons of package conflicts...

>@tkralphs the best course of action would be to install a Miniforge distribution from here: https://github.com/conda-forge/miniforge#miniforge3 and then install "conda-build" inside there (in the base environment, ideally). >Then there should...

I doubt I can be very helpful here, but it seems funny that the package name and feedstock name (`cylp`) don't match the name of the subdirectory where the recipe...