-
Notifications
You must be signed in to change notification settings - Fork 132
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
[ArPow] Onboard runtime to arcade-powered source-build #2052
Comments
Here's the current state on this work. It's a little complicated because there's an active breaking change between Arcade and Runtime that I think is still playing out: https://github.com/dotnet/core-eng/issues/12264 For now, I have a branch of Arcade that needs to be plugged into dotnet/runtime. Paths that I'll use later:
I run my build in The docker host is a bare-metal Linux (Fedora) machine. (1) In (2) Make changes like these to dotnet/runtime to accept the local arcade build: diff --git a/NuGet.config b/NuGet.config
index d99698bf530..5b1340214d9 100644
--- a/NuGet.config
+++ b/NuGet.config
@@ -13,2 +13,3 @@
<!-- TEST_RESTORE_SOURCES_INSERTION_LINE -->
+ <add key="local-arcade" value="/work/sandbox" />
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
diff --git a/global.json b/global.json
index cb70ea2b691..7b32916853c 100644
--- a/global.json
+++ b/global.json
@@ -15,3 +15,3 @@
"Microsoft.DotNet.Build.Tasks.TargetFramework.Sdk": "6.0.0-beta.21081.1",
- "Microsoft.DotNet.Arcade.Sdk": "6.0.0-beta.21081.1",
+ "Microsoft.DotNet.Arcade.Sdk": "6.0.0-dev",
"Microsoft.DotNet.Helix.Sdk": "6.0.0-beta.21081.1", (3) Copy the Arcade build into the local feed and build: git clean -xdff
mkdir sandbox # This name happens to be in the .gitignore, nothing special.
cp -r ~/git/arcade/artifacts/packages/Debug/NonShipping/ sandbox
centosme -- ./build.sh -c Release --restore --build --pack /p:ArcadeBuildFromSource=true /p:SourceBuildNonPortable=true -bl
Once dotnet/runtime gets to a version of Arcade >= |
No description provided.
The text was updated successfully, but these errors were encountered: