rustc: reason(s) for linker options should be introspectable/reported via command line switch #1307
Labels
A-diagnostics
Area: Error and warning messages generated by Cargo itself.
A-linkage
Area: linker issues, dylib, cdylib, shared libraries, so
S-needs-design
Status: Needs someone to work further on the design for the feature or fix. NOT YET accepted.
Sunday Aug 03, 2014 at 05:45 GMT
For earlier discussion, see rust-lang/rust#16210
This issue was labelled with: A-tools, I-enhancement in the Rust repository
I tried to build gfx-rs on my mac yesterday.
I thought I had it working, but then when I tried to build the cube example that it includes, I hit a linker error:
So, here is the issue: I see we have
-framework OpenGL
in the invocation. But there is also-lGL
and-lX11
in the above command. And I have no idea which crate (gfx-rs
has many subcrates it pulls in viacargo
) is injecting which of those linker directives.This bug is for fixing the implicit tooling issue here (not about fixing
gfx-rs
itself to work on OS X). From what I can see from skimmingcargo's
source code, the linker directives are not being inserted bycargo
, but rather byrustc
; but there is no way for me to modify therustc
command line thatcargo
gives me to find out more information about which crate(s) is the source for each linker flag.The text was updated successfully, but these errors were encountered: