-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Conversation
x86 debug was red around time of triggering... test Windows_NT x86 Debug Build |
@dotnet-bot test Windows_NT x86 Debug Build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me. I assume there needs to be some VSO work to enable the new build leg in the official builds (which only MSFT employees have access to). So I don't think this can be merged until then. @johnbeisner - will you be doing this?
@livarcocc - is this something we want to take for the .NET Core 2.1 release? Should it be integrated into a 2.1.300 branch? Or is this post-2.1 work?
I think this PR is probably dependent on getting new runtime bits with necessary tools i.e. #9015. @johnbeisner Said in #8896 (comment) that he set up VSO with triggers off. The arm64 links are still not populated, so it looks like someone needs to establish triggers. I would like to see this included in 2.1 branch, so that if and when we stabilize the arm64 runtime, we can use the cli. |
4bb94d0
to
ab1d77c
Compare
@johnbeisner Thanks. I can't see into your link so I don't exactly know what it means. I am hoping it means that the arm64 linux is link in the readme will soon be populated. https://dotnetcli.blob.core.windows.net/dotnet/Sdk/master/dotnet-sdk-latest-linux-arm64.tar.gz |
Based on https://dotnet.myget.org/feed/dotnet-core/package/nuget/runtime.linux-arm64.Microsoft.NETCore.App Needs 26407-01 or better. |
src/redist/redist.csproj
Outdated
@@ -257,7 +257,7 @@ | |||
</Target> | |||
|
|||
<Target Name="CrossgenPublishDir" | |||
Condition=" '$(DISABLE_CROSSGEN)' == '' And !$(Architecture.StartsWith('arm')) " | |||
Condition=" '$(DISABLE_CROSSGEN)' == '' And !('$(Architecture)' == 'arm') " |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
ab1d77c
to
879bf9c
Compare
I missed that the core-setup dependencies were updated 2 days ago. Fixed nit above. Rebased to pick up crosscomponent crossgen from core-setup. Crossgen should work now. @eerhardt Please trigger 'test ci please' |
879bf9c
to
b37a11b
Compare
@dotnet-bot test Ubuntu16.04 x64 Debug Build |
@dotnet-bot test ci please |
Can this be merged? It would be nice to include in 2.1 |
@livarcocc @johnbeisner - thoughts on merging? |
@eerhardt |
Not that I know of. I think @sdmaclea's main concern is |
linux-arm is slightly more complicated. The current linux-arm crosscomponent needs to run on x86 not x64. @echesakovMSFT was working on enabling x64_arm crosscomponents. |
We do have a docker container that supports See https://github.com/dotnet/core-setup/pull/3892/files for the docker tag. |
It was just too complicated for me to figure out how to enable linux-arm. Enabling for linux-arm64 was trivial. |
Yep - I think that's totally fine. You are enabling |
@sdmaclea |
@johnbeisner This depends on coresetup 26407-01 or better (#9044 on master) which has not yet merged into dotnet/cli:release/2.1.3xx. Perhaps this should merge on the master branch first? Let me know how you want me to proceed. |
b37a11b
to
c4e427d
Compare
Rebased to the current master tip for now pending instructions. |
Looks like this can be rebased on 2.1.3xx after #9076 merges |
c4e427d
to
83a8646
Compare
It is already done |
@sdmaclea We have decided to not take this change for 2.1 and instead move it to 2.2. 2.2 is were most of the support for this will come anyways and we felt it was going to be better there. Could you please re-target to master (again, sorry) and then we can merge this. |
83a8646
to
ade3573
Compare
"This" ? linux-arm64?
Done |
test Windows_NT_ES x64 Debug Build |
Enable Arm64 Crossgen
Fixes for arm64 #8998
Depends on dotnet/core-setup#3987 ++
Works if I manually copy crossgen dependencies from core-setup
@eerhardt
Contains #8896 which I hope/expect will merge before dotnet/core-setup#3987 is ready