Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upDo static linking by default #10209
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Nominating, though I think we can live without this for 1.0 |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
P-low, not necessary to do this (or decide about doing it) for 1.0. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
wycats
Nov 14, 2013
Contributor
As an embedded user of Rust, this would be really really nice and would make 1.0 significantly more appealing.
|
As an embedded user of Rust, this would be really really nice and would make 1.0 significantly more appealing. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
+1 for static linking by default |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
I believe that as it stands today #10740 blocks this bug. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
alexcrichton
Dec 17, 2013
Member
Now that #10740 is closed, I'm still not entirely convinced that we should do this by default. This makes linking fn main() {} 4.5x slower from 20ms to 90ms, which is a pretty noticeable hit when dealing with small programs. We should investigate how to optimize compile times for small programs and then I believe that static linking would be an excellent default.
|
Now that #10740 is closed, I'm still not entirely convinced that we should do this by default. This makes linking |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
alexcrichton
Jan 19, 2014
Member
Closing, we prefer static linking by default, and #11253 is the tracker for whether we should output an rlib or a dylib by default for libraries.
|
Closing, we prefer static linking by default, and #11253 is the tracker for whether we should output an rlib or a dylib by default for libraries. |
brson commentedOct 31, 2013
I currently believe there is little hope that Rust libraries can offer any meaningful binary forward compatibility or upgradability. Since this is one of the primary benefits of dynamic linking (the other being reduction in code size), and static linking having other advantages of convenience, perhaps we should prefer static linking by default.
cc #10208 #10188