MeloNX/Ryujinx-ryubing
10
0
Fork 0
Code Issues 184 Pull Requests 15 Actions Packages Projects Releases 36 Wiki Activity

[Feature Request] Remove x64 files from MacOS release. #341

New Issue
Open
opened 2024-12-03 13:10:41 +00:00 by Otozinclus · 5 comments
Otozinclus commented 2024-12-03 13:10:41 +00:00 (Migrated from github.com)
Copy Link

Overview

Only include ARM64 files in the official Mac release (or make 2 seperate versions for x64/arm)

Smaller details

You can specify in the build command if you want to build it universal, for x64 or Arm64

Nature of request

Remove unnecessary files to cut size in half

Why would this feature be useful?

Ryujinx is pretty much broken on Intel Macs and never got official support for them. Yet, the x64 binaries are still included into the MacOS release, nearly doubling the size of the file. Ryujinx is not as big in the first place, but considering the Mac x64 version is broken, I think it makes sense to offer a Mac ARM64 only version, as there isn't really a drawback and you cut the file size in half.

If there is a use case for the x64 compatibility unknown to me, maybe just splitting them up into 2 separate released could be a option as well.

### Overview Only include ARM64 files in the official Mac release (or make 2 seperate versions for x64/arm) ### Smaller details You can specify in the build command if you want to build it universal, for x64 or Arm64 ### Nature of request Remove unnecessary files to cut size in half ### Why would this feature be useful? Ryujinx is pretty much broken on Intel Macs and never got official support for them. Yet, the x64 binaries are still included into the MacOS release, nearly doubling the size of the file. Ryujinx is not as big in the first place, but considering the Mac x64 version is broken, I think it makes sense to offer a Mac ARM64 only version, as there isn't really a drawback and you cut the file size in half. If there is a use case for the x64 compatibility unknown to me, maybe just splitting them up into 2 separate released could be a option as well.
👍 1
mfield01 commented 2024-12-04 01:30:39 +00:00 (Migrated from github.com)
Copy Link

It runs well on x64 macs if built with an older .Net sdk — 8.0.200 is fine, for example.

It runs well on x64 macs if built with an older .Net sdk — 8.0.200 is fine, for example.
Otozinclus commented 2024-12-05 20:20:29 +00:00 (Migrated from github.com)
Copy Link

It runs well on x64 macs if built with an older .Net sdk — 8.0.200 is fine, for example.

What I am talking about though is not removing x86 support entirely, just from the official releases that get published automatically. The official release does not use 8.0.200 for building anyway, I think so at least (please correct me if I am wrong), for that you need to self compile Ryujinx and if you self compile, you can manually select the ISA you want to have included yourself

> It runs well on x64 macs if built with an older .Net sdk — 8.0.200 is fine, for example. What I am talking about though is not removing x86 support entirely, just from the official releases that get published automatically. The official release does not use 8.0.200 for building anyway, I think so at least (please correct me if I am wrong), for that you need to self compile Ryujinx and if you self compile, you can manually select the ISA you want to have included yourself
samnelly4real commented 2024-12-08 10:11:07 +00:00 (Migrated from github.com)
Copy Link

Nice idea💡💡💡💡💡💡

Nice idea💡💡💡💡💡💡
mfield01 commented 2025-02-12 04:32:14 +00:00 (Migrated from github.com)
Copy Link

Just bumping this to note that the .Net bug that was breaking emulation on intel macs has been fixed, and the newest Canary builds work fine again (I checked Ryujinx 1.2.379.)

Just bumping this to note that the .Net bug that was breaking emulation on intel macs has been fixed, and the newest Canary builds work fine again (I checked Ryujinx 1.2.379.)
GreemDev commented 2025-02-12 04:34:05 +00:00 (Migrated from github.com)
Copy Link

Just bumping this to note that the .Net bug that was breaking emulation on intel macs has been fixed, and the newest Canary builds work fine again (I checked Ryujinx 1.2.379.)

The issue with Intel Macs run deeper than a .NET bug.

> Just bumping this to note that the .Net bug that was breaking emulation on intel macs has been fixed, and the newest Canary builds work fine again (I checked Ryujinx 1.2.379.) The issue with Intel Macs run deeper than a .NET bug.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
audio
Affects Audio playback during emulation
blocked on external progress
This cannot move forward without work on an external project or service.
bug
Something isn't working
cpu
An issue with ARMeilleure, the JIT, or Hypervisor
documentation
Improvements or additions to documentation
duplicate
This issue or pull request already exists
enhancement
New feature or request
good first issue
Good first issues to work on for new contributors
gpu
Affects GPU emulation
graphics-backend:metal
Affects the Metal Graphics backend
graphics-backend:opengl
Affects the OpenGL Graphics backend
graphics-backend:vulkan
Affects the Vulkan Graphics backend
gui
Affects the Avalonia UI or translations.
help wanted
Extra attention is needed
horizon
Affects the Horizon OS HLE components.
infra
Updates to dependencies
invalid
This doesn't seem right
kernel
Affects the kernel HLE components.
ldn
Affects the LDN functionality
linux
Linux only issue
macOS
macOS only issue
not planned but open to a PR
I do not intend on working on this myself, but I would not be opposed to an implementation.
question
Further information is requested
windows
Windows only issue
wontfix
This will not be worked on
No Label
enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MeloNX/Ryujinx-ryubing#341
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?