Replies: 3 comments
-
It seems I can connect my retro handheld to my Windows build which does not have the compatiblity adjustment. This is good news. |
Beta Was this translation helpful? Give feedback.
-
Compatibility is enforced via the build version number ( The git commit will be different since you used |
Beta Was this translation helpful? Give feedback.
-
There is currently no git describe on the port's menu screen, presumably because it's forked and scons couldn't grab the info it wanted. Like I said before, though, I don't believe maintaining compatibility for an outdated custom firmware is in my best interest, nor yours. If I do create future builds for debian arm64, I will end support for ArkOS plain and simple. |
Beta Was this translation helpful? Give feedback.
-
Last week I created a compatibility branch on forked dxx-rebirth and modified
valptridx.h
in commit JeodC@c22de97. This allows the port to run on operating systems that use older GLIBC (and compiles on bullseye).I never found out what the ramifications for this are. Since I didn't build from this repo, I assume git headers and hashes are different. Does this mean my port's multiplayer will be restricted? If so, are there any workarounds I can do?
Are there any other possible ramifications I could encounter by using the above commit?
Thanks in advance. @vLKp
Beta Was this translation helpful? Give feedback.
All reactions