bin cc

A build-time dependency for Cargo build scripts to assist in invoking the native C compiler to compile native C code into a static archive to be linked into Rust code.

19 stable releases

1.0.18 Jul 11, 2018
1.0.17 May 29, 2018
1.0.14 Apr 29, 2018
1.0.9 Mar 21, 2018
0.0.1 Dec 16, 2014

#1 in Development tools

Download history 46144/week @ 2018-05-06 52151/week @ 2018-05-13 53440/week @ 2018-05-20 47857/week @ 2018-05-27 55575/week @ 2018-06-03 53405/week @ 2018-06-10 44332/week @ 2018-06-17 47090/week @ 2018-06-24 50148/week @ 2018-07-01 47536/week @ 2018-07-08 58474/week @ 2018-07-15 60108/week @ 2018-07-22 48881/week @ 2018-07-29

221,945 downloads per month


A library to compile C/C++/assembly into a Rust library/application.

Build Status Build status


A simple library meant to be used as a build dependency with Cargo packages in order to build a set of C/C++ files into a static archive. This crate calls out to the most relevant compiler for a platform, for example using cl on MSVC.

Note: this crate was recently renamed from the gcc crate, so if you're looking for the gcc crate you're in the right spot!

Using cc-rs

First, you'll want to both add a build script for your crate (build.rs) and also add this crate to your Cargo.toml via:

cc = "1.0"

Next up, you'll want to write a build script like so:

// build.rs

extern crate cc;

fn main() {

And that's it! Running cargo build should take care of the rest and your Rust application will now have the C files foo.c and bar.c compiled into a file named libfoo.a. You can call the functions in Rust by declaring functions in your Rust code like so:

extern {
    fn foo_function();
    fn bar_function();

pub fn call() {
    unsafe {

fn main() {
    // ...

External configuration via environment variables

To control the programs and flags used for building, the builder can set a number of different environment variables.

  • CFLAGS - a series of space separated flags passed to compilers. Note that individual flags cannot currently contain spaces, so doing something like: "-L=foo\ bar" is not possible.
  • CC - the actual C compiler used. Note that this is used as an exact executable name, so (for example) no extra flags can be passed inside this variable, and the builder must ensure that there aren't any trailing spaces. This compiler must understand the -c flag. For certain TARGETs, it also is assumed to know about other flags (most common is -fPIC).
  • AR - the ar (archiver) executable to use to build the static library.

Each of these variables can also be supplied with certain prefixes and suffixes, in the following prioritized order:

  1. <var>_<target> - for example, CC_x86_64-unknown-linux-gnu
  2. <var>_<target_with_underscores> - for example, CC_x86_64_unknown_linux_gnu
  3. <build-kind>_<var> - for example, HOST_CC or TARGET_CFLAGS
  4. <var> - a plain CC, AR as above.

If none of these variables exist, cc-rs uses built-in defaults

In addition to the the above optional environment variables, cc-rs has some functions with hard requirements on some variables supplied by cargo's build-script driver that it has the TARGET, OUT_DIR, OPT_LEVEL, and HOST variables.

Optional features


Currently cc-rs supports parallel compilation (think make -jN) but this feature is turned off by default. To enable cc-rs to compile C/C++ in parallel, you can change your dependency to:

cc = { version = "1.0", features = ["parallel"] }

By default cc-rs will limit parallelism to $NUM_JOBS, or if not present it will limit it to the number of cpus on the machine. If you are using cargo, use -jN option of build, test and run commands as $NUM_JOBS is supplied by cargo.

Compile-time Requirements

To work properly this crate needs access to a C compiler when the build script is being run. This crate does not ship a C compiler with it. The compiler required varies per platform, but there are three broad categories:

  • Unix platforms require cc to be the C compiler. This can be found by installing cc/clang on Linux distributions and Xcode on OSX, for example.
  • Windows platforms targeting MSVC (e.g. your target triple ends in -msvc) require cl.exe to be available and in PATH. This is typically found in standard Visual Studio installations and the PATH can be set up by running the appropriate developer tools shell.
  • Windows platforms targeting MinGW (e.g. your target triple ends in -gnu) require cc to be available in PATH. We recommend the MinGW-w64 distribution, which is using the Win-builds installation system. You may also acquire it via MSYS2, as explained here. Make sure to install the appropriate architecture corresponding to your installation of rustc. GCC from older MinGW project is compatible only with 32-bit rust compiler.

C++ support

cc-rs supports C++ libraries compilation by using the cpp method on Build:

extern crate cc;

fn main() {
        .cpp(true) // Switch to C++ library compilation.

When using C++ library compilation switch, the CXX and CXXFLAGS env variables are used instead of CC and CFLAGS and the C++ standard library is linked to the crate target.

CUDA C++ support

cc-rs also supports compiling CUDA C++ libraries by using the cuda method on Build (currently for GNU/Clang toolchains only):

extern crate cc;

fn main() {
        // Switch to CUDA C++ library compilation using NVCC.
        // Generate code for Maxwell (GTX 970, 980, 980 Ti, Titan X).
        // Generate code for Maxwell (Jetson TX1).
        // Generate code for Pascal (GTX 1070, 1080, 1080 Ti, Titan Xp).
        // Generate code for Pascal (Tesla P100).
        // Generate code for Pascal (Jetson TX2).


This project is licensed under either of

at your option.


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Serde by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

MIT/Apache-2.0 license


Reverse deps