Proposal: Publish nethost static library#8659
Proposal: Publish nethost static library#8659nxtn wants to merge 2 commits intodotnet:masterfrom nxtn:nethost
Conversation
|
The packaging infra work looks good, nice. I'm not familiar with the consequences of shipping this, e.g. signing, delivering both the dynamic |
|
I looked at what we do for other libraries. For example CRT prepends So in that case it would be In any case it's an explicit action to use this in a build, so people can pick one easily and there should be no naming issues I'm aware of. As for the signing: I don't know what our policies are shipping unsigned code, but since it is not an executable itself, I think it should be fine. @GrabYourPitchforks would know for sure I think. |
|
The |
|
On Unix, libraries are usually always prefixed with "lib" and postfixed with something like ".so" (ELF systems) or ".dylib" (Mach-O systems) or ".a" (in case of static libraries). Which one gets picked depends on how the compiler driver is instructed to call the linker (with e.g. the In other words, I find it kind of confusing to have the static library having the prefix and the shared library without it: to link with the static library, you'd pass |
|
@lpereira On Linux/Mac the shared library does have the prefix - it should be (already) called:
Now we would be basically adding |
See discussion in #7114
Using "s" suffix as a temporary workaround to distinguish between static/import libraries.