Closed DimitriPapadopoulos closed 1 year ago
Interesting. In conda-build 2 we use to mix build tools and dependencies in the same environment. This caused a variety of headaches, which finally led to us splitting them in conda-build 3 into build tools and the host environment (where libraries are linked to).
The resolution error here seems to imply that build tools (like cmake
) are installed in the same environment as library dependencies that z5 links to. A reasonable fix would be to split these environments apart. This is a bit easier to do when building a recipe (since conda-build has this logic baked in), but one might be able to achieve the same thing just with conda (without conda-build) by using environment stacking. IOW create an environment of build tools and another environment with libraries z5 links to and then stack them.
Yes, indeed there is just a single env for now: https://github.com/constantinpape/z5/blob/master/.github/workflows/environment.yaml.
This is a bit easier to do when building a recipe (since conda-build has this logic baked in), but one might be able to achieve the same thing just with conda (without conda-build) by using environment stacking. IOW create an environment of build tools and another environment with libraries z5 links to and then stack them.
Interesting. I don't have time to look into this myself right now, but happy to review / help out a bit.
Nor do I unfortunately. Was hoping the info would be useful/helpful for whoever might have interest & time
It works without a single change on my side. Incompatibilities have been fixed directly in the stack.
Looks like there are quite a number of incompatibilities in the stack: