Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

output filename collision on windows #15086

Open
rgbav opened this issue Jan 21, 2025 · 1 comment
Open

output filename collision on windows #15086

rgbav opened this issue Jan 21, 2025 · 1 comment
Labels
A-layout Area: target output directory layout, naming, and organization C-bug Category: bug O-windows OS: Windows S-triage Status: This issue is waiting on initial triage.

Comments

@rgbav
Copy link

rgbav commented Jan 21, 2025

Problem

This seems to be a known issue. I just want to report, in case it is not known on windows.
The problem occured on the starter project (https://github.com/leptos-rs/start)

warning: output filename collision.
The bin target `leptos-portfolio` in package `leptos-portfolio v0.1.0 (D:\Repos\leptos-portfolio)` has the same output filename as the lib target `leptos_portfolio` in package `leptos-portfolio v0.1.0 (D:\Repos\leptos-portfolio)`.
Colliding filename is: D:\Repos\leptos-portfolio\target\debug\deps\leptos_portfolio.pdb
The output filenames should be unique.
Consider changing their names to be unique or compiling them separately.
This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>.
If this looks unexpected, it may be a bug in Cargo. Please file a bug report at
https://github.com/rust-lang/cargo/issues/ with as much information as you
can provide.
cargo 1.83.0 (5ffbef321 2024-10-29) running on `x86_64-pc-windows-msvc` target `x86_64-pc-windows-msvc`
First unit: Unit { pkg: Package { id: PackageId { name: "leptos-portfolio", version: "0.1.0", source: "D:\\Repos\\leptos-portfolio" }, ..: ".." }, target: TargetInner { name: "leptos-portfolio", doc: true, ..: with_path("D:\\Repos\\leptos-portfolio\\src/main.rs", Edition2021) }, profile: Profile { ..: default_dev() }, kind: Host, mode: Build, features: ["ssr"], rustflags: [], rustdocflags: [], links_overrides: {}, artifact: false, artifact_target_for_features: None, is_std: false, dep_hash: 14176037005699255033 }
Second unit: Unit { pkg: Package { id: PackageId { name: "leptos-portfolio", version: "0.1.0", source: "D:\\Repos\\leptos-portfolio" }, ..: ".." }, target: TargetInner { name_inferred: true, ..: lib_target("leptos_portfolio", ["cdylib", "rlib"], "D:\\Repos\\leptos-portfolio\\src\\lib.rs", Edition2021) }, profile: Profile { ..: default_dev() }, kind: Host, mode: Build, features: ["ssr"], rustflags: [], rustdocflags: [], links_overrides: {}, artifact: false, artifact_target_for_features: None, is_std: false, dep_hash: 12242921020153376879 }

Steps

  1. Use Windows
  2. cargo leptos new --git https://github.com/leptos-rs/start
  3. cargo leptos watch

Possible Solution(s)

No response

Notes

No response

Version

cargo 1.83.0 (5ffbef321 2024-10-29)
release: 1.83.0
commit-hash: 5ffbef3211a8c378857905775a15c5b32a174d3b
commit-date: 2024-10-29
host: x86_64-pc-windows-msvc
libgit2: 1.8.1 (sys:0.19.0 vendored)
libcurl: 8.9.0-DEV (sys:0.4.74+curl-8.9.0 vendored ssl:Schannel)
os: Windows 10.0.22631 (Windows 11 Professional) [64-bit]
@rgbav rgbav added C-bug Category: bug S-triage Status: This issue is waiting on initial triage. labels Jan 21, 2025
@epage epage added the O-windows OS: Windows label Jan 21, 2025
@epage
Copy link
Contributor

epage commented Jan 21, 2025

This is noted in #6313. Unsure if we want a separate issue or to have it rolled up

@epage epage added the A-layout Area: target output directory layout, naming, and organization label Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-layout Area: target output directory layout, naming, and organization C-bug Category: bug O-windows OS: Windows S-triage Status: This issue is waiting on initial triage.
Projects
None yet
Development

No branches or pull requests

2 participants