Skip to content
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

[VMR] Pass target architecture on Windows #19321

Merged
merged 2 commits into from
Apr 5, 2024
Merged

[VMR] Pass target architecture on Windows #19321

merged 2 commits into from
Apr 5, 2024

Conversation

akoeplinger
Copy link
Member

We didn't pass an explicit architecture so it always used the host one, even for arm64/x86 builds.

Contributes to dotnet/source-build#4292

We didn't pass an explicit architecture so it always used the host one, even for arm64/x86 builds.

Contributes to dotnet/source-build#4292
@ViktorHofer
Copy link
Member

Should we also pass the TargetOS in, in case we would ever want to cross-build on Windows, i.e. for Browser?

@akoeplinger
Copy link
Member Author

Yeah good idea.

@akoeplinger akoeplinger enabled auto-merge (squash) April 5, 2024 11:27
@akoeplinger
Copy link
Member Author

/azp run installer-unified-build-full

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@akoeplinger akoeplinger merged commit caadf5c into main Apr 5, 2024
58 of 67 checks passed
@akoeplinger akoeplinger deleted the vmr-target-arch branch April 5, 2024 12:52
@ViktorHofer
Copy link
Member

Thanks. Do we have a tracking issue for the -cross switch not known error on Windows?

@akoeplinger
Copy link
Member Author

Ugh I should have disabled auto-merge ...

I think -cross doesn't make sense on Windows, we only really use it for Linux.

akoeplinger added a commit to dotnet/runtime that referenced this pull request Apr 5, 2024
Fixes VMR build error on Windows after dotnet/installer#19321

We haven't used or passed this on Windows before and a bunch of logic is conditioned based on the `CrossBuild` property (which is what `-cross` is turned into in build.sh) so ignore it for now.
akoeplinger added a commit to dotnet/runtime that referenced this pull request Apr 5, 2024
Fixes VMR build error on Windows after dotnet/installer#19321

We haven't used or passed this on Windows before and a bunch of logic is conditioned based on the `CrossBuild` property (which is what `-cross` is turned into in build.sh) so ignore it for now.
matouskozak pushed a commit to matouskozak/runtime that referenced this pull request Apr 30, 2024
Fixes VMR build error on Windows after dotnet/installer#19321

We haven't used or passed this on Windows before and a bunch of logic is conditioned based on the `CrossBuild` property (which is what `-cross` is turned into in build.sh) so ignore it for now.
Ruihan-Yin pushed a commit to Ruihan-Yin/runtime that referenced this pull request May 30, 2024
Fixes VMR build error on Windows after dotnet/installer#19321

We haven't used or passed this on Windows before and a bunch of logic is conditioned based on the `CrossBuild` property (which is what `-cross` is turned into in build.sh) so ignore it for now.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants