Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build portability is complicated by recent zlib-ng updates #351

Open
ctsa opened this issue Apr 22, 2022 · 0 comments
Open

Build portability is complicated by recent zlib-ng updates #351

ctsa opened this issue Apr 22, 2022 · 0 comments

Comments

@ctsa
Copy link

ctsa commented Apr 22, 2022

I'd like to use rust-htslib in an application where we can retain a straightforward build process for open-source users. One benchmark for this use case is to ask how hard it is to build the tool for a Centos7 cluster without root.

Prior to the 0.38.0 release, rust-htslib wasn't complicating build portability by the above criteria - centos7 + stock gcc + rustup seemed to be sufficient. The new changes adding zlib-ng support now require cmake v3.12+, which I can't find a way to workaround with feature selection, e.g. default-features = false. Is there a feature switch which would remove the cmake requirement or at least reduce it to cmake 2.8?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant