We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently the package only pulls in the Windows version of the runtime packages:
runtime.win-x64.Microsoft.DotNet.ILCompiler.LLVM
It should do this for the version that it is running against. #54 is trying to solve that issue
The work around is is to add the package then run:
dotnet add runtime.linux-x64.Microsoft.DotNet.ILCompiler.LLVM
The text was updated successfully, but these errors were encountered:
As far as I am aware, there is no NuGet mechanism to pull in a RID-specific package based on the host (SDK's) RID.
(There is an undocumented mechanism for doing so with target RIDs.)
I think the simplest way forward here is to make the SDK package itself RID-specific, i. e. publish:
BytecodeAlliance.Componentize.DotNet.Wasm.SDK.linux-x64 BytecodeAlliance.Componentize.DotNet.Wasm.SDK.win-x64 ...
With the consumption side being:
<PackageReference Include="BytecodeAlliance.Componentize.DotNet.Wasm.SDK.$(NETCoreSdkPortableRuntimeIdentifier)" />
Then adding dependencies on anything host-RID-specific becomes very simple.
The alternative to this is manually downloading and caching the host-specific content.
Sorry, something went wrong.
jsturtevant
Successfully merging a pull request may close this issue.
Currently the package only pulls in the Windows version of the runtime packages:
It should do this for the version that it is running against. #54 is trying to solve that issue
Workaround
The work around is is to add the package then run:
The text was updated successfully, but these errors were encountered: