I updated the error states to use say_status.
Add text to the empty error
The empty error looked odd with the say_status change.
Update all stderr messages
Switch them to format statements and create a helper for the error
status.
The package id for path dependencies now has another path component pointing
precisely to the package being compiled, so lots of tests need their output
matches to get updated.
There was a failure mode of the handling of the rerun-if-changed directive where
it would rerun the build script twice before hitting a steady state of actually
processing the directives. The order of events that led to this were:
1. A project was built from a clean directory. Cargo recorded a fingerprint
indicating this (for the build script), but the fingerprint indicated that
the build script was a normal build script (no manually specified inputs)
because Cargo had no prior knowledge.
2. A project was then rebuilt from the same directory. Cargo's new fingerprint
for the build script now indicates that there is a custom list of
dependencies, but the previous fingerprint indicates there wasn't, so the
mismatch causes another rebuild.
3. All future rebuilds will agree that there are custom lists both before and
after, so the directives are processed as one would expect.
This commit does a bit of refactoring in the fingerprint module to fix this
situation. The recorded fingerprint in step (1) is now recorded as a "custom
dependencies are specified" fingerprint if, after the build script is run,
custom dependencies were specified.
Closes#2267
This should allow compiling the specified target in the various profiles that
are available to it, e.g. bench or test in addition to the standard
dev.
Closes#2120
- `build_with_args_to_one_of_multiple_binaries`, verify that only one bin gets built
- `fails_with_args_to_all_binaries`
- `build_with_args_to_one_of_multiple_tests`, same behavious as for the binaries
- `build_foo_with_bar_dependency`, verify that bar dependency gets built and only foo gets compiled with args
- `build_only_bar_dependency`, build the bar package, that foo depends, on with the extra args
- An error will be returned if the length of `targets` is not 1
- The profile of `targets` gets cloned in order to append the extra arguments.
- The new test verifies that the build fails due to both `lib` and `main` being compiled
- The new tests verifies that the extra arguments gets appended to the command. One is for lib and one is for main
- Currently the arguments gets passed on to *every* target that gets built, so the tests only contain one file each
