Where should I place a static library so I can link it with a Rust program?

Question

I do not know how to link a C library to Rust. Here's what I have done:

My lib.rs file contains

#[link(name = "test")] extern { 

The library is built and has the name libtest.a.

I do not know where to put it. I have tried several places, but I still have errors of this type when doing cargo run

error: linking with `cc` failed: exit code: 1 //.. note: /usr/bin/ld: no se puede encontrar -ltest note: /usr/bin/ld: no se puede encontrar -ltest note: /usr/bin/ld:....... //.. 

Translation of the above /usr/bin/ld: no se puede encontrar -ltest -> usr/bin/ld: cannot find -ltest

I do not know where to put libtest.a so that /usr/bin/ld can find it. Cargo does not tell me where the library should be in the project.

My Cargo.toml contains

[dependencies.test] path = "./src/test"  [dependencies] bitflags = "0.7" libc = "0.2"  [build-dependencies] make-cmd = "0.1" 

After reading the FFI section of the documentation again, I thought that maybe the error messages from before were because I was looking for a shared library, so I made the following changes:

#[link(name = "test", kind = "static")] 

After these changes, I still do not know how to indicate where the library is, but the message now tells me this:

error: could not find native static library `test`, perhaps an -L flag is missing? 

Answer 1

Where should I place a static library

Wherever you want. You have to tell the compiler where to find it.

---

First, let's create a static library

$ cat hello.c int square(int value) {   return value * value; } $ gcc -c -o hello.o hello.c $ ar rcs libhello.a hello.o 

Next, we use a build script to set the value of rustc-link-search to point to the directory where I put the library:

fn main() {     println!("cargo:rustc-link-search=/Projects/stack-overflow/using-c-static/"); } 

We can now use the functions from the library:

#[link(name = "hello")] extern "C" {     fn square(val: i32) -> i32; }  fn main() {     let r = unsafe { square(3) };     println!("3 squared is {}", r); } 

---

That's the basic functionality. You could also use the build script to specify which library to link, instead of having it in your code (rustc-link-lib). I prefer this because then the two configurations are right next to each other.

You should also probably follow the *-sys naming convention and create a crate dedicated to exposing the underlying API. Importantly, this crate should specify the link manifest key to avoid duplicate symbols at linking time.

If your build script needs more information, cargo passes many parameters via environment variables.

If you are compiling C code as part of your crate, you should look into crates like cc or cmake, which make the act of building a piece of software much easier.