rust/src/librustc_resolve/Cargo.toml

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

[lib]
name = "rustc_resolve"
path = "lib.rs"
crate-type = ["dylib"]
test = false

[dependencies]
log = "0.3"
syntax = { path = "../libsyntax" }
rustc = { path = "../librustc" }
arena = { path = "../libarena" }
rustc_errors = { path = "../librustc_errors" }
syntax_pos = { path = "../libsyntax_pos" }
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies. 2016-01-21 17:19:23 -06:00			`[package]`
			`authors = ["The Rust Project Developers"]`
			`name = "rustc_resolve"`
			`version = "0.0.0"`

			`[lib]`
			`name = "rustc_resolve"`
			`path = "lib.rs"`
			`crate-type = ["dylib"]`
rustbuild: Add support for crate tests + doctests This commit adds support to rustbuild to run crate unit tests (those defined by `#[test]`) as well as documentation tests. All tests are powered by `cargo test` under the hood. Each step requires the `libtest` library is built for that corresponding stage. Ideally the `test` crate would be a dev-dependency, but for now it's just easier to ensure that we sequence everything in the right order. Currently no filtering is implemented, so there's not actually a method of testing only libstd or only libcore, but rather entire swaths of crates are tested all at once. A few points of note here are: * The `coretest` and `collectionstest` crates are just listed as `[[test]]` entires for `cargo test` to naturally pick up. This mean that `cargo test -p core` actually runs all the tests for libcore. * Libraries that aren't tested all mention `test = false` in their `Cargo.toml` * Crates aren't currently allowed to have dev-dependencies due to rust-lang/cargo#860, but we can likely alleviate this restriction once workspaces are implemented. cc #31590 2016-04-29 16:23:15 -05:00			`test = false`
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies. 2016-01-21 17:19:23 -06:00
			`[dependencies]`
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 09:57:59 -06:00			`log = "0.3"`
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies. 2016-01-21 17:19:23 -06:00			`syntax = { path = "../libsyntax" }`
			`rustc = { path = "../librustc" }`
			`arena = { path = "../libarena" }`
Move errors from libsyntax to its own crate 2016-06-21 17:08:13 -05:00			`rustc_errors = { path = "../librustc_errors" }`
			`syntax_pos = { path = "../libsyntax_pos" }`