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

Support some method of determining if a symbol is available in dynamic libraries #586

Open
ericonr opened this issue Mar 5, 2021 · 1 comment

Comments

@ericonr
Copy link

ericonr commented Mar 5, 2021

Hi!

As it stands, most -sys crates, together with even libc, can't query if an external library contains a certain symbol or not. This makes it so these crates target a specific version of a library, instead of being able to adapt to changes in such libraries (for example libgit2-sys and the issues in rust-lang/libc#1848), unless one is using bindgen or similar.

I am aware this crate doesn't want to carry functionality for generating binaries or dynamic libraries (#46, #250, #458), but, as far as I know, those are the only two ways to make the linker check if all symbols can be resolved, which would in turn allow for "primitive" feature detection.

I'd like to use such a feature to implement rust-lang/libc#2088 (comment). Do you think it's feasible to build it atop cc-rs, or, given this justification, do you think cc-rs could carry it?

@mqudsi
Copy link
Contributor

mqudsi commented May 21, 2024

fyi I maintain rsconf which has only cc-rs as a dependency and implements the functionality required for build scripts, such as target.has_symbol() or target.has_library(). We built this for use in fish-shell when we ported from C++ to rust over the past two years.

Unlike libc's "based off target-triple" approach, we feature detect specific libc features such as pipe2() or posix_spawn() so we can more gracefully handle older versions of the same system/architecture.

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

2 participants