-
Notifications
You must be signed in to change notification settings - Fork 107
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
external rom support #467
Comments
You either have to change the code, or you can try replacing the |
If we ever get this app on the store we can easily add small features like this (sigh) |
....OR you can always edit But NOTE MAME4iOS will still assume |
hey thanks for brainstorming some ideas. I think the first thing I did was create symlink (soft) and i think due to containerization, it scope is limited to inside the container directory. I might be wrong about this so when I reboot into macOS, I’ll give editing the .ini a shot as well! |
hi! I totally understand MAME4mac is built under the same kind of containerized sandbox iOS has.
The issue (and sure this is the case with a lot of peeps) is large rom sets tend to reside on an external drive and/or network share (eg. NAS)
Is there any way to trick MAME4mac to using a roms folder outside of
~/Library/Containers/com.example.mame4ios/Data/Documents/roms
?I'm looking for something along the lines of a bind mount like is available in Docker.
If anyone has gotten this to work, I'd love to know what steps you took!
The text was updated successfully, but these errors were encountered: