sccache | sccache is ccache with cloud storage

by mozilla Rust Version: 0.7.7 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | sccache Summary

sccache is a Rust library. sccache has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

sccache is a [ccache] compiler caching tool. It is used as a compiler wrapper and avoids compilation when possible, storing cached results either on [local disk] #local) or in one of [several cloud storage backends] #storage-options). sccache includes support for caching the compilation of C/C++ code, [Rust] docs/Rust.md), as well as NVIDIA’s CUDA using [nvcc] sccache also provides [icecream] distributed compilation (automatic packaging of local toolchains) for all supported compilers (including Rust). The distributed compilation system includes several security features that icecream lacks such as authentication, transport layer encryption, and sandboxed compiler execution on build servers. See [the distributed quickstart] docs/DistributedQuickstart.md) guide for more information.

Support

Quality

Security

License

Reuse

Support

sccache has a medium active ecosystem.

It has 4338 star(s) with 457 fork(s). There are 43 watchers for this library.

There were 1 major release(s) in the last 6 months.

There are 287 open issues and 444 have been closed. On average issues are closed in 50 days. There are 13 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of sccache is 0.7.7

Quality

sccache has 0 bugs and 0 code smells.

Security

sccache has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

sccache code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

sccache is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

sccache releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of sccache

Get all kandi verified functions for this library.

sccache Key Features

No Key Features are available at this moment for sccache.

sccache Examples and Code Snippets

No Code Snippets are available at this moment for sccache.

Community Discussions

Trending Discussions on sccache

errors when building electron from source with gn and ninja on Mac OS 10.15

Alpine dockerfile: "cannot produce proc-macro...does not support these crate types"

What exactly is a 'crate' in the Cargo ecosystem and what is the mapping to what is on crates.io?

QUESTION

errors when building electron from source with gn and ninja on Mac OS 10.15

Asked 2019-Nov-19 at 14:43

at the moment, I try to fix some accessibility bugs in electron. For that, I had tried to build electron from source. The source isn't edited or changed from me, so it is original.

I pulled the source from the official repo on GitHub, following the building instructions and I had used the client and so on.

Here is the output of my steps in the terminal under Mac OS X 10.15:

...

ANSWER

Answered 2019-Nov-19 at 06:27

Chromium seems to have updated its code for macOS 10.15. You can find the updated code here. https://github.com/chromium/chromium/commit/961e7821b9356445f48e5ce2c077c40c2c6b2309

Source https://stackoverflow.com/questions/58794301

QUESTION

Alpine dockerfile: "cannot produce proc-macro...does not support these crate types"

Asked 2019-Sep-18 at 12:58

Total rust noob here. Trying to build a sccache binary for linux x64 with Redis: true. I'm starting with an alpine image:

...

ANSWER

Answered 2019-Sep-17 at 15:50

The proc_macro crate relies on a couple of features only available to dynamically-linked executables, and since musl is anything but that, you cannot use proc_macro on musl.

The issue related to this is here, and Alex describes quite well some of the issues and tradeoffs that'd need to be made to make this crate available on full static targets: https://github.com/rust-lang/rust/issues/40174

Just to confirm from the container:

Source https://stackoverflow.com/questions/57965805

QUESTION

What exactly is a 'crate' in the Cargo ecosystem and what is the mapping to what is on crates.io?

Asked 2018-Aug-29 at 18:53

I am a little confused as to the exact things hosted on crates.io (is a 'crate' the proper way to refer to those)? My understanding is that a crate is a unit of compilation in Rust, but then what is the mapping between crates and what is on crates.io? For instance, The Rust Programming Language appendix on macros says that since there can only be one procedural macro per crate:

Our two crates are tightly related, so we create the procedural macro crate within the directory of our hello_macro crate. If we change the trait definition in hello_macro, we’ll have to change the implementation of the procedural macro in hello_macro_derive as well. The two crates will need to be published separately, and programmers using these crates will need to add both as dependencies and bring them both into scope. We could instead have the hello_macro crate use hello_macro_derive as a dependency and reexport the procedural macro code. But the way we’ve structured the project makes it possible for programmers to use hello_macro even if they don’t want the derive functionality.

It has to be published separately on crates.io. This seems pretty clear: a crate on crates.io is the same as a local crate, and the mapping is one-to-one.

However, when discussing projects with both an executable and a library, it implies that they are separate crates but needn't be published separately. For instance, the sccache repo has both main.rs and lib.rs. Is the separate binary crate not actually stored on crates.io and resides in the repo only? Then how does cargo install figure out what to install?

What is a "package"?

I tried to run cargo package with a sample project that contains both binary and library targets. And both were added to the .cargo file (by the way, is the exact format of .cargo archives documented anywhere?). This still leaves me confused. Can we publish multiple crates as a part of one package? Should we then refer to what is stored on crates.io as packages? Am I right to assume that each package can contain multiple binary crates but only one library crate? This is my current understanding.

...

ANSWER

Answered 2018-Aug-29 at 18:53

The exact things hosted on crates.io are crates inside packages.

A crate is the output artifact of the compiler.

From Rust Reference Manual:

The compilation model centers on artifacts called crates. Each compilation processes a single crate in source form, and if successful, produces a single crate in binary form: either an executable or some sort of library.

A package is an artifact managed by Cargo, the Rust package manager.

Cargo.toml manifest file defines the package with the syntax:

Source https://stackoverflow.com/questions/52024304

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install sccache

There are prebuilt x86-64 binaries available for Windows, Linux (a portable binary compiled against musl), and macOS [on the releases page](https://github.com/mozilla/sccache/releases/latest). Several package managers also include sccache packages, you can install the latest release from source using cargo, or build directly from a source checkout.
sccache is a [Rust](https://www.rust-lang.org/) program. Building it requires cargo (and thus rustc). sccache currently requires Rust 1.43.0. We recommend you install Rust via [Rustup](https://rustup.rs/).
If you are building sccache for non-development purposes make sure you use cargo build --release to get optimized binaries:. By default, sccache builds with support for all storage backends, but individual backends may be disabled by resetting the list of features and enabling all the other backends. Refer the [Cargo Documentation](http://doc.crates.io/manifest.html#the-features-section) for details on how to select features with Cargo.
When building with the gcs feature, sccache will depend on OpenSSL, which can be an annoyance if you want to distribute portable binaries. It is possible to statically link against OpenSSL using the openssl/vendored feature.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: