This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages) This article uses bare URLs, which are uninformative and vulnerable to link rot. Please consider converting them to full citations to ensure the article remains verifiable and maintains a consistent citation style. Several templates and tools are available to assist in formatting, such as Reflinks (documentation), reFill (documentation) and Citation bot (documentation). (August 2022) (Learn how and when to remove this template message) This article may be too technical for most readers to understand. Please help improve it to make it understandable to non-experts, without removing the technical details. (October 2022) (Learn how and when to remove this template message) (Learn how and when to remove this template message)

In software engineering, a compatibility layer is an interface that allows binaries for a legacy or foreign system to run on a host system. This translates system calls for the foreign system into native system calls for the host system. With some libraries for the foreign system, this will often be sufficient to run foreign binaries on the host system. A hardware compatibility layer consists of tools that allow hardware emulation.


Examples include:

Compatibility layer in kernel:

A compatibility layer avoids both the complexity and the speed penalty of full hardware emulation. Some programs may even run faster than the original, e.g. some Linux applications running on FreeBSD's Linux compatibility layer may perform better than the same applications on Red Hat Linux. Benchmarks are occasionally run on Wine to compare it to Windows NT-based operating systems.[10]

Even on similar systems, the details of implementing a compatibility layer can be quite intricate and troublesome; a good example is the IRIX binary compatibility layer in the MIPS architecture version of NetBSD.[11]

A compatibility layer requires the host system's CPU to be (upwardly) compatible to that of the foreign system. For example, a Microsoft Windows compatibility layer is not possible on PowerPC hardware because Windows requires an x86 CPU. In this case full emulation is needed.


Hardware compatibility layers involve tools that allow hardware emulation. Some hardware compatibility layers involve breakout boxes because breakout boxes can provide compatibility for certain computer buses that are otherwise incompatible with the machine.

See also


  1. ^ Charlie Russel, Microsoft MVP for Windows Server and Tablet PC (2002-02-18). "Application Compatibility in Windows XP".
  2. ^ "Cygwin". Retrieved 2019-11-23.
  3. ^
  4. ^ "Tizen OS will run Android apps -- with a little help from third-party software (Video)".
  5. ^ "Linux emulation in FreeBSD".
  6. ^ "Emulation". Retrieved 2014-03-16.
  7. ^ "A look inside..." Retrieved 2014-03-16.
  8. ^ "NetBSD Binary Emulation". Retrieved 2014-03-16.
  9. ^ "Comparing WSL 1 and WSL 2".
  10. ^ BenchMark-0.9.5 Archived 2010-12-09 at the Wayback Machine - The Official Wine Wiki
  11. ^ Emmanuel Dreyfus (August 8, 2002). "IRIX Binary Compatibility, Part 1". Archived from the original on 2017-10-21. Retrieved 2014-03-16.