`--artifact-dir` (nee `--out-dir`) Tracking Issue
Note: this was renamed from `--out-dir` to `--artifact-dir` in #13809 Original issue: #4875 Implementation PR: #5203 Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#artifact-dir Issues: https://github.com/rust-lang/cargo/labels/Z-out-dir **Summary** Adds `--artifact-dir=PATH` flag to `cargo build` to specify a directory to place final artifacts. **Tasks:** - [x] #5203 - [x] #13809 - [x] Remove `--out-dir` - [ ] Switch `--artifact-dir` to being the directory we uplift directly into with a fallback to the current location (done across all commands including `cargo package`) - [ ] Evaluate recording requested uplifts and performing them at the end - [ ] Evaluate only creating `examples/` if needed (helps if we know a priori what is uplifted) - [ ] Detect conflicts in uplifts due to platform-tuple not being included - [ ] *(design needed)* explore templating of artifact-dir - [ ] Rework to better match https://github.com/rust-lang/cargo/issues/14125#issuecomment-2258708917 **Unresolved questions** - [ ] Multi-target builds (`--target <one> --target <two>`) - [ ] #7493 - [x] #6100 — concern about similarity with `--target-dir`, proliferation of flags - [x] #6313 — concern about name collisions in workspaces or with examples - [x] What exactly is the use case for this? In what scenario would it be used where you don't already have an outer build system or script that can copy the files into the correct location? - [x] Confusion with rustc's `--ou
Posted by ehuss on Mar 28, 2019, 9:24 PM
Tags
Related issues
- [Meta] Feedback on granular control over Copilot changes
- unexpected status 401 Unauthorized issue
- [MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
- [CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
- Video stops playing after some minutes
- [MODEL] Claude verbose code comments by default — ignores instructions to stop.
Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments
github (Software)
[Meta] Feedback on granular control over Copilot changes
unexpected status 401 Unauthorized issue
[MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
[CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
Video stops playing after some minutes
[MODEL] Claude verbose code comments by default — ignores instructions to stop.
Scope Codex VS Code chats to the current workspace/project
Update on "Co-authored-by: Copilot" in commit messages
`--artifact-dir` (nee `--out-dir`) Tracking Issue
Note: this was renamed from `--out-dir` to `--artifact-dir` in #13809 Original issue: #4875 Implementation PR: #5203 Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#artifact-dir Issues: https://github.com/rust-lang/cargo/labels/Z-out-dir **Summary** Adds `--artifact-dir=PATH` flag to `cargo build` to specify a directory to place final artifacts. **Tasks:** - [x] #5203 - [x] #13809 - [x] Remove `--out-dir` - [ ] Switch `--artifact-dir` to being the directory we uplift directly into with a fallback to the current location (done across all commands including `cargo package`) - [ ] Evaluate recording requested uplifts and performing them at the end - [ ] Evaluate only creating `examples/` if needed (helps if we know a priori what is uplifted) - [ ] Detect conflicts in uplifts due to platform-tuple not being included - [ ] *(design needed)* explore templating of artifact-dir - [ ] Rework to better match https://github.com/rust-lang/cargo/issues/14125#issuecomment-2258708917 **Unresolved questions** - [ ] Multi-target builds (`--target <one> --target <two>`) - [ ] #7493 - [x] #6100 — concern about similarity with `--target-dir`, proliferation of flags - [x] #6313 — concern about name collisions in workspaces or with examples - [x] What exactly is the use case for this? In what scenario would it be used where you don't already have an outer build system or script that can copy the files into the correct location? - [x] Confusion with rustc's `--ou
Comments (0)
No comments yet. Start the discussion.