-
Notifications
You must be signed in to change notification settings - Fork 136
Make Source-Build Portable Build Compatible #4418
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
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Is this a duplicate of #2932? |
It's similar/has the same end goal. I think the difference is that as of the creation of the current issue, we have the ability to "technically" build source-build with a portable RID/portable build property set, but the build itself is not actually portable due to bugs. Not sure if that was possible when Rich created the other issue? |
See dotnet/installer#15163 (comment) for a fix that Nix folks used. |
Based on dotnet/sdk#40843, it's clear that while the VMR is configured to be portable, source build does not work in a portable state due to bugs.
For example, while certain OSs build successfully with PortableBuild=true (centos9 for example), the produced SDK does not work. An example is the following run of the scenario tests with a source-build SDK that was built using the PortableBuild=true property:
Another example of source-build being portable build incompatible is the fact that aspnetcore fails to build on alpine:
In the above error message, aspnetcore fails to build because it is looking for the linux-x64 version of crossgen. Earlier, this package was built and outputted as
Microsoft.NETCore.App.Crossgen2.linux-musl-x64
. See dotnet/sdk#40843 (comment)The text was updated successfully, but these errors were encountered: