You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently working on a bioconda recipe for a tool depending on rust-htslib.
I've got a working version, but it seems the rust compilation chain still pulls in lots of C sources, via hts-sys I guess, when, naively, I had envisioned that I could just specify the existing htslib conda package as a host requirement and have rust-htslib link to it.
What's your take on how a best-practice recipe requiring rust-htslib should be set up? @johanneskoester maybe?
... and connected to that, would it be of value to have a dedicated rust-htslib bioconda package that other recipes could depend on?
The text was updated successfully, but these errors were encountered:
Hi. The other recipes on bioconda also use hts-sys this way, i.e. statically linked. Hence, adding htslib as a dependency would not help. However, one could of course try to enhance hts-sys such that it can also use a shared library. In that case the dependency would help. I think this would however require some code/setup changes there.
I'm currently working on a bioconda recipe for a tool depending on rust-htslib.
I've got a working version, but it seems the rust compilation chain still pulls in lots of C sources, via hts-sys I guess, when, naively, I had envisioned that I could just specify the existing htslib conda package as a host requirement and have rust-htslib link to it.
What's your take on how a best-practice recipe requiring rust-htslib should be set up? @johanneskoester maybe?
... and connected to that, would it be of value to have a dedicated rust-htslib bioconda package that other recipes could depend on?
The text was updated successfully, but these errors were encountered: