-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Teach rustpkg how to probe for C libraries and header files #6404
Comments
See also how cmake handles this. IMO autotools' method is hacky, slow, and ill-fit for a new tool. We don't need to probe for endianness and such either (rustc already knows that because it knows what architecture it is targetting). A lot of the things autotools checks for have been standardized and are consistent across platforms (it checks for all the standard C headers and unix tools, for example, and the existence of lots of standard functions). I think cmake's solution is a lot better, but it's not without its own set of perils (you need to actually write out configs for each library and so on). Latching on to pkg-config would be good too. |
Visiting for triage. Not an immediate priority. |
Triage: no change. #2124 is similar (rustc being able to read such headers). |
rustpkg is gone, and I think #2124 covers the still relevant part of this well |
Rustup r? `@ghost` changelog: none
Sub-bug of #5677
See discussion at https://etherpad.mozilla.org/Rustpkg-Servo-meeting, starting with "If we had something to replace AC_CHECK_HEADER and AC_CHECK_LIB in the pkg.rs script..."
The text was updated successfully, but these errors were encountered: