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
warning: file found to be present in multiple build targets #5930
Comments
This can happen when there are two targets (like two |
Yes that's exactly the case. |
i have this same warning but a different situation. im trying to build a library with tests... and a build script so i can generate tests from a list of files, at compile time.
this layout is based on paholg's post here https://stackoverflow.com/questions/34662713/how-can-i-create-parameterized-tests-in-rust thanks |
Oh oops I meant to close this earlier as @gnzlbg's original bug was discovered and presumably fixed. @donbright mind actually opening a new issue for that as I think it's a new use case we haven't seen before! |
This is exactly what I want, could I disable this warning? Or this better way to generate multiple binaries with same source file? Maybe I should create a section
And then create two file with different name but same content in |
Yeah @liuchong we'd recommend either using a library or a |
Thanks! @alexcrichton |
In the cargo-asm project cargo produces the warning:
Since it is a warning, I assume that I must be doing something wrong / not as good as possible there, and that there is something that I can do to silence it.
I have no idea what that can be:
cargo-asm
produces two binaries,cargo-asm
andcargo-llvm-ir
, both are identical. Ideally, I'd just produce one, and then create a link with a different name to it, or a copy. I have no idea how to do any of that with cargo.If there is nothing that users can do about this warning, then it shouldn't be a warning until there is something that users can do.
The text was updated successfully, but these errors were encountered: