crate_type = "lib" means a dynamic lib

[pcwalton]

It should mean a static lib.

[metajack]

Should lib mean build both since it's unspecific?

[alexcrichton]

I have defined this in the manual as the "compiler recommended" format of library. When I initially added rlibs, they weren't good enough to make the default. I believe that may have changed now, so perhaps it could become the default.

I'm a little wary of generating both formats, but it's an interesting idea and may actually be the best thing to do. Regardless, this warrants discussion.

[jhasse]

+1 for creating a static lib (this means rlib, right?).

What would the use case be for creating both?

[jhasse]

What should happen if crate_type isn't set?

I've implemented static lib as a default and it breaks a lot of tests ... :/

[alexcrichton]

staticlib and rlib are two different outputs. The compiler will attempt to link rlibs together, and the compiler will never look at staticlibs (staticlibs are meant for integration with existing projects).

I do not believe the default should change until we have discussed this further.

[pnkfelix]

Assigning to P-high. (I'm not 100% convinced that there isn't a backcompat risk; but that depends on how one defines the relationship between docs, users, and backcompat.)

[alexcrichton]

We decided in today's meeting to continue making lib a platform-specific default. We also decided to make it rlib instead of dylib as it is today.