rust/src/librustc_back/Cargo.toml

[package]
authors = ["The Rust Project Developers"]
name = "rustc_back"
version = "0.0.0"

[lib]
name = "rustc_back"
path = "lib.rs"
crate-type = ["dylib"]

[dependencies]
syntax = { path = "../libsyntax" }
serialize = { path = "../libserialize" }
log = "0.3"

[features]
jemalloc = []
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies. 2016-01-21 15:19:23 -08:00			`[package]`
			`authors = ["The Rust Project Developers"]`
			`name = "rustc_back"`
			`version = "0.0.0"`

			`[lib]`
			`name = "rustc_back"`
			`path = "lib.rs"`
			`crate-type = ["dylib"]`

			`[dependencies]`
			`syntax = { path = "../libsyntax" }`
			`serialize = { path = "../libserialize" }`
Remove internal liblog This commit deletes the internal liblog in favor of the implementation that lives on crates.io. Similarly it's also setting a convention for adding crates to the compiler. The main restriction right now is that we want compiler implementation details to be unreachable from normal Rust code (e.g. requires a feature), and by default everything in the sysroot is reachable via `extern crate`. The proposal here is to require that crates pulled in have these lines in their `src/lib.rs`: #![cfg_attr(rustbuild, feature(staged_api, rustc_private))] #![cfg_attr(rustbuild, unstable(feature = "rustc_private", issue = "27812"))] This'll mean that by default they're not using these attributes but when compiled as part of the compiler they do a few things: * Mark themselves as entirely unstable via the `staged_api` feature and the `#![unstable]` attribute. * Allow usage of other unstable crates via `feature(rustc_private)` which is required if the crate relies on any other crates to compile (other than std). 2017-02-15 07:57:59 -08:00			`log = "0.3"`
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies. 2016-01-21 15:19:23 -08:00
			`[features]`
			`jemalloc = []`