-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Closed
Labels
A-compiletestArea: The compiletest test runnerArea: The compiletest test runnerA-testsuiteArea: The testsuite used to check the correctness of rustcArea: The testsuite used to check the correctness of rustcC-bugCategory: This is a bug.Category: This is a bug.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Description
When we use the "auxiliary crate" feature in compile-test, it adds a -L <aux-path>
flag that points rustc at the directory where to find those crates. This means that when rustc sees an extern crate
it then searches those directories. It's good to have the ability to test that behavior, but it's not the way that cargo drives rustc -- and as a result it's not compatible with the new extern-prelude feature set, requiring awkward run-make tests like extern-prelude.
It would probably be better for compiletest, by default, to add a --extern foo=<path-to-foo>
flag for each auxiliary crate. We could maybe keep a way to use the "auxdir" option.
petrochenkov
Metadata
Metadata
Assignees
Labels
A-compiletestArea: The compiletest test runnerArea: The compiletest test runnerA-testsuiteArea: The testsuite used to check the correctness of rustcArea: The testsuite used to check the correctness of rustcC-bugCategory: This is a bug.Category: This is a bug.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)