Conversation

Notices

1. Embed this notice
   Rich Felker (dalias@hachyderm.io)'s status on Sunday, 24-Nov-2024 19:01:37 JST Rich Felker

   in reply to

   • mcc
   • Misty

   @misty @mcc I think there's a standard idiom for making cargo packages that wrap C libraries.

   • Embed this notice
     mcc (mcc@mastodon.social)'s status on Sunday, 24-Nov-2024 19:01:38 JST mcc

     in reply to

     • Misty

     @misty this… sounds like cargo? What do you mean by "check for"? The normal rust tooling is biased to npm style per project library checkouts and static linking, not system libraries per se

     When you say build scripts you mean something OUTSIDE rust/cargo?

   • Embed this notice
     Misty (misty@digipres.club)'s status on Sunday, 24-Nov-2024 19:01:38 JST Misty

     in reply to

     • mcc

     @mcc Sorry, by "static library" I mean a C library - not something provided by Cargo itself. Cargo provides the ability to write Rust build scripts that are executed during the build to handle things like this; I'm just wondering if there's something easier than writing the whole "fetch this release tarball, unpack, build, etc." logic myself.

     https://doc.rust-lang.org/cargo/reference/build-scripts.html

   • Embed this notice
     Misty (misty@digipres.club)'s status on Sunday, 24-Nov-2024 19:01:39 JST Misty

     Rust folks: is there a dead-easy “check for this C library or download a source tarball and build a static library" thing for build scripts? I want to set up a dependency for something if I can but I really don't want to maintain any real complex buildscripts.