Skip to content
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

Statically link native libraries into singlefilehost on OSX and Windows #43699

Closed
VSadov opened this issue Oct 21, 2020 · 6 comments
Closed

Statically link native libraries into singlefilehost on OSX and Windows #43699

VSadov opened this issue Oct 21, 2020 · 6 comments
Assignees

Comments

@VSadov
Copy link
Member

VSadov commented Oct 21, 2020

Currently we only support this on Linux.
We should extend the support to other supported/tested platforms.

Prerequisite:#41299

@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added area-Infrastructure-libraries untriaged New issue has not been triaged by the area owner labels Oct 21, 2020
@ghost
Copy link

ghost commented Oct 21, 2020

Tagging subscribers to this area: @safern, @ViktorHofer
See info in area-owners.md if you want to be subscribed.

@ghost
Copy link

ghost commented Oct 21, 2020

Tagging subscribers to this area: @agocke, @vitek-karas
See info in area-owners.md if you want to be subscribed.

@VSadov VSadov removed area-Infrastructure-libraries untriaged New issue has not been triaged by the area owner labels Oct 21, 2020
@VSadov VSadov self-assigned this Oct 21, 2020
@agocke
Copy link
Member

agocke commented Oct 21, 2020

Dup of #43072?

@VSadov
Copy link
Member Author

VSadov commented Oct 21, 2020

@agocke - #43072 is about statically linking the components of the runtime (JIT, VM, GC), while this is about native libraries that live in libs partition - Like clrcompression.dll, libSystem.Net.Security.Native.so, ibSystem.Security.Cryptography.Native.Apple.dylib and the like.

Each platform has some of these in the bundle (and needs to extract), except Linux that currently has all it needs statically linked, but does it in a way that would not work for Windows and OSX, so we should switch it to a more cross-platform friendly plan as well.

The problems that need to be solved are very different, so it makes sense to do these separately and track separately.

@VSadov
Copy link
Member Author

VSadov commented Oct 21, 2020

Switching to a cross-platform linking of libs is tracked in #41299.
We may that separately and before this workitem or just do them together.

(similar to doing #43423 first, which just made code more cross-platform friendly and then do #43556)

@danmoseley danmoseley changed the title Statically link native libraries into singlfilehost on OSX and Windows Statically link native libraries into singlefilehost on OSX and Windows Nov 24, 2020
@ghost ghost added in-pr There is an active PR which will close this issue when it is merged and removed in-pr There is an active PR which will close this issue when it is merged labels Dec 18, 2020
@VSadov
Copy link
Member Author

VSadov commented Dec 18, 2020

@VSadov VSadov closed this as completed Dec 18, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Jan 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants