-
Notifications
You must be signed in to change notification settings - Fork 252
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
[Question] How to create separate NuGet packages for OS specific native components #6083
Comments
Maybe create a package that imports build targets, which add package references based on the RID? |
@emgarten Could you point me in the right direction? |
The current guidance is that packages should put all RID specific assemblies in the same package instead of splitting them up. I don't believe there are docs on how to use runtime.json for this currently. There have been concerns raised about it being used out side of the System.* packages. @ericstj @davidfowl should runtime.json be documented for splitting up packages? |
The caveats need to be explained, but we should document it. @conniey The downside is that the consumer of your package has to specify which RID they want to get assets for at restore time. |
Details about Problem
I am trying to create a NuGet package that is a C# wrapper around ic4c. It has a set of native dlls that need to be compiled for each OS. I don't want to include it into a single NuGet package because the DLLs are 27MB for each OS. I noticed that the .NET team has NuGet packages like:
runtime.ubuntu.14.04-x64.runtime.native.system.io.compression
that contain assets only for that OS.Is there guidance on how to create those packages? I tried to find documentation on docs.microsoft.com and this repository but was unable to.
Thanks,
Connie
The text was updated successfully, but these errors were encountered: