fix(test-harness): hax-engine-names-extract
needs hax in PATH
#628
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit fixes the test harness: since
#428, the test harness silently assumes hax is in PATH while building the crate
hax-engine-names-extract
.This crate
hax-engine-names-extract
is used at build time by the engine to list and import the Rust names we rely on.hax-engine-names-extract
itself requires the Rust part of hax at build time.This PR fixes the test harness so that:
cargo-hax
and the drivercargo-hax
& driver just built (somewhere local intarget/bin/something/someting
), injects thoses paths as env vars in acargo build --bin hax-engine-names-extract
;Tagging @Nadrieril who found that bug, thanks!