build: make laze use Cargo's dependency info #651
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kaspar030
commented
Dec 29, 2024
|
|
||
| let depfile = args.output_file.with_extension("d"); | ||
| std::fs::write(depfile, &depstr).unwrap(); | ||
| let depfile = args.output_file.with_extension("dd"); |
There was a problem hiding this comment.
that's a debug leftover :)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR makes use of some dependency trickery so we're able to drop the
always: truefrom our cargo rule. This extracts Cargo's source file deps for each application crate, and additionally adds a script to get a list of all Cargo.toml in the workspace.Issues/PRs references
Depends on kaspar030/laze#599 to be in the used laze release.
Open Questions
Change checklist