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

Publishing static library should also publish other necessary static libs #1733

Closed
MichalStrehovsky opened this issue Nov 18, 2021 · 4 comments
Labels
area-NativeAOT-coreclr .NET runtime optimized for ahead of time compilation

Comments

@MichalStrehovsky
Copy link
Member

MichalStrehovsky commented Nov 18, 2021

We should either binplace the required static libraries (the appropriate Runtime.lib flavor, ClrCompression, etc.) to the publish output to make it easier to consume this or produce some artifact (RSP file fragment for example?) that has the paths.

@MichalStrehovsky MichalStrehovsky added the area-NativeAOT-coreclr .NET runtime optimized for ahead of time compilation label Nov 18, 2021
@kkptm
Copy link

kkptm commented Nov 22, 2021

is there a plan for this work?

@CXCubeHD
Copy link

CXCubeHD commented Sep 5, 2022

This should become much higher priority since it is so painful to compile these libraries manually. I tried it and I was unsuccessful

@ceztko
Copy link

ceztko commented Nov 20, 2023

Maybe a valuable option to have would be to output a newline separated list of paths, which can be easily parsed for example with cmake and piped to linker options.

@MichalStrehovsky
Copy link
Member Author

Tracked in dotnet/runtime#70277.

@MichalStrehovsky MichalStrehovsky closed this as not planned Won't fix, can't repro, duplicate, stale Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-NativeAOT-coreclr .NET runtime optimized for ahead of time compilation
Projects
None yet
Development

No branches or pull requests

4 participants