Editing Compatibility layers

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 141: Line 141:
 
|[https://old.reddit.com/r/openKylin/comments/14u5kad/about_kmre/ KMRE]
 
|[https://old.reddit.com/r/openKylin/comments/14u5kad/about_kmre/ KMRE]
 
|align=left|{{Icon|Linux}}
 
|align=left|{{Icon|Linux}}
|[https://archive.ubuntukylin.com/ubuntukylin/pool/partner/kmre_2.4.6.8+22.04_amd64.deb 2.4.6.8]</br>[https://archive.kylinos.cn/kylin/KYLIN-ALL/pool/universe/k/kmre/kmre_2.4.8.7-0k0.9_amd64.deb 2.4.8.7-0k0.9]<ref group=A name=kmrex86>2.4.8.7 is untested-NeoKylin never announced nor shipped this with x86 releases</ref>
+
|[https://archive.ubuntukylin.com/ubuntukylin/pool/partner/kmre_2.4.6.8+22.04_amd64.deb 2.4.6.8]
 
|{{?}} ||{{~}} ||{{✗}}
 
|{{?}} ||{{~}} ||{{✗}}
|Allows openKylin/Ubuntu Kylin to run Android applications.
+
|Allows openKylin to run Android applications.
 
|-
 
|-
 
!colspan="7"|ARM
 
!colspan="7"|ARM
Line 211: Line 211:
 
|[https://old.reddit.com/r/openKylin/comments/14u5kad/about_kmre/ KMRE]
 
|[https://old.reddit.com/r/openKylin/comments/14u5kad/about_kmre/ KMRE]
 
|align=left|{{Icon|LinuxARM}}
 
|align=left|{{Icon|LinuxARM}}
|[https://archive.kylinos.cn/kylin/KYLIN-ALL/pool/universe/k/kmre/kmre_2.4.8.7-0k0.9_arm64.deb 2.4.8.7-0k0.9]</br>[https://archive.kylinos.cn/kylin/KYLIN-ALL/pool/universe/k/kmre/kmre_2.5.0.2-0k0.1tablet3_arm64.deb 2.5.0.2-0k0.1tablet3]<ref group=A name=kmrearm>2.5.0.2 is only for some industrial tablets or similar devices with Phytium processors. Regular desktop devices should continue with 2.4.8.7 .</ref>
+
|?
 
|{{?}} ||{{~}} ||{{✗}}
 
|{{?}} ||{{~}} ||{{✗}}
|Allows openKylin/NeoKylin (with supported processors) to run Android applications.
+
|Allows openKylin to run Android applications.
 
|-
 
|-
 
!colspan="9"|Console
 
!colspan="9"|Console
Line 231: Line 231:
 
|x86 Linux programs<abbr title="into LoongArch64 instruction set">*</abbr>
 
|x86 Linux programs<abbr title="into LoongArch64 instruction set">*</abbr>
 
|}
 
|}
<references group=A />
+
 
 
===Comparisons===
 
===Comparisons===
 
*[[Wine]] is a free and open-source compatibility layer that aims to allow computer programs (application software and computer games) developed for Microsoft Windows to run on Unix-like operating systems, primarily Linux and macOS. Since late 2017 there is also an experimental build for Android. Wine is almost as old as the Linux project, starting in the summer of 1993. Today it's widely used, very popular and sponsored by companies such as CodeWeavers and Valve. The core Wine development aims at a correct implementation of the Windows API as a whole. In this regard it's similar to the [[MAME]] project in its focus on correctness over usability. There are a lot of versions/forks of Wine which focus of different goals, such as usability, compatibility, gaming, office applications, etc. A few are listed below, Wikipedia has [[wikipedia:Wine_(software)#Other_versions_of_Wine|a more complete list]].
 
*[[Wine]] is a free and open-source compatibility layer that aims to allow computer programs (application software and computer games) developed for Microsoft Windows to run on Unix-like operating systems, primarily Linux and macOS. Since late 2017 there is also an experimental build for Android. Wine is almost as old as the Linux project, starting in the summer of 1993. Today it's widely used, very popular and sponsored by companies such as CodeWeavers and Valve. The core Wine development aims at a correct implementation of the Windows API as a whole. In this regard it's similar to the [[MAME]] project in its focus on correctness over usability. There are a lot of versions/forks of Wine which focus of different goals, such as usability, compatibility, gaming, office applications, etc. A few are listed below, Wikipedia has [[wikipedia:Wine_(software)#Other_versions_of_Wine|a more complete list]].
Line 244: Line 244:
 
* KMRE is a compatibility layer and it's the official solution to run Android applications on computers with Chinese homegrown Phytium/KunPeng ARM processors and NeoKylin Linux operating system, though later also available on x86-64 on [https://www.ubuntukylin.com/index-en.html Ubuntu Kylin]. KMRE is not designed with third-party applications outside its app store and in fact, force installing third-party apps breaks older versions of KMRE. It's the go-to solution if you are restricted to working with these kinds of computers due to national security reasons.
 
* KMRE is a compatibility layer and it's the official solution to run Android applications on computers with Chinese homegrown Phytium/KunPeng ARM processors and NeoKylin Linux operating system, though later also available on x86-64 on [https://www.ubuntukylin.com/index-en.html Ubuntu Kylin]. KMRE is not designed with third-party applications outside its app store and in fact, force installing third-party apps breaks older versions of KMRE. It's the go-to solution if you are restricted to working with these kinds of computers due to national security reasons.
 
* Vita2hos is an early compatibility layer for Nintendo Switch that runs PlayStation Vita applications natively. Only able to load simple test homebrews such as vita-8 as of December 2022. Appears to only be developed every once in a while.
 
* Vita2hos is an early compatibility layer for Nintendo Switch that runs PlayStation Vita applications natively. Only able to load simple test homebrews such as vita-8 as of December 2022. Appears to only be developed every once in a while.
 
 
==Wrappers==
 
==Wrappers==
 
Compatibility layers may also make use of '''wrappers''', which translate a specific graphics API to another. How the user sets up the wrapper varies between each project but most involve a drop-in replacement of the original libraries.
 
Compatibility layers may also make use of '''wrappers''', which translate a specific graphics API to another. How the user sets up the wrapper varies between each project but most involve a drop-in replacement of the original libraries.
Line 252: Line 251:
 
[[Category:Compatibility layers]]
 
[[Category:Compatibility layers]]
 
[[Category:Not really emulators]]
 
[[Category:Not really emulators]]
----
 
{{NEL}}
 

Please note that all contributions to Emulation General Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Emulation General Wiki:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)