Specify runtime identifier during build #77
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
needs an approve from maintainer to verify, that it actually works in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, when building Ryujinx for windows, if we don't specify
-r win-x64, theRuntimeIdentifiervariable becomes empty, which results inARMMeilleure.csprojincludinglibarmeilleure-jitsupport.dylibfile for windows, which is unwanted, because.dylibisosx-arm64only file.This PR aims at removing the mentioned file by specifying the runtime identifier during build.
So now, the resulting build for osx-arm64looks like this:
and for windows like this:
Also, I have verified the
dotnet build -c Release -r osx-arm64is still working on M1 MacOS