Mike Sarahan
Mike Sarahan
cc1plus may be hard-coded in your recipe's source code somewhere. Our compiler tools are all prefixed. See https://conda.io/docs/user-guide/tasks/build-packages/compiler-tools.html#using-the-compiler-packages for more info. You probably need to patch your makefile or otherwise...
Here's a good guide on patches: https://github.com/ilastik/ilastik/wiki/Creating-patches-for-Conda-recipes You might need to explicitly list a c++ compiler, in addition to c: {{ compiler("c") }} {{ compiler("cxx") }}
/ok to test
/merge
We will be sure to PR anything that we create. No idea on timeline, though. Hopefully soon.
I've seen it, but I'm not a developer on this project. Hopefully someone at Enthought will see your contribution here.
Added some Continuum/Anaconda context https://github.com/jaimergp/conda-forge.github.io/pull/1
This is a really wonderful collaboration and trip down memory lane! I have one more PR with line breaks and a couple of other links at https://github.com/jaimergp/conda-forge.github.io/pull/2
Great idea! Thanks. That will serve the purpose of avoiding unexpected updates, which is our biggest problem. Lockfiles would still be nice to avoid paying the solving cost, but that's...
I have set up Airspeed Velocity for conda with some simple, very high level benchmarks. See https://github.com/conda/conda-benchmarks for the code and https://conda.github.io/conda-benchmarks for results. Note that each commit takes about...