You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When bootstrapping a new OS (or just building .NET Core from source in general), there are times when I don't have the exact version of the SDK that source-build wants. One case is where I build a bootstrap SDK, run a source-build, and then use the output of that first source-build to build again.
We currently export the SDK_VERSION environment variable based on the value in DotnetCLIVersion.txt:
I would hope we could get rid of all the places that need this SDK_VERSION, but that is a long-term goal.
In the meantime, we should instead get the correct version of the SDK we are using instead of the one that is checked into source. That way people don't need to edit source files just to get the build to work.
We can get the SDK version by executing dotnet --version.
The text was updated successfully, but these errors were encountered:
One case is where I build a bootstrap SDK, run a source-build, and then use the output of that first source-build to build again.
I had the same use case and the same exact issue.
A more general fix to improve this use case might be to provide the path to an entire SDK (not just the version) to the build. Source build can just pick it up from there and use it.
We should document the minimum/maximum version required for the SDK too.
When bootstrapping a new OS (or just building .NET Core from source in general), there are times when I don't have the exact version of the SDK that source-build wants. One case is where I build a bootstrap SDK, run a source-build, and then use the output of that first source-build to build again.
We currently export the SDK_VERSION environment variable based on the value in DotnetCLIVersion.txt:
source-build/build.sh
Line 6 in ac7159e
We can get the SDK version by executing
dotnet --version
.The text was updated successfully, but these errors were encountered: