© 2018 Focusrite Audio Engineering Plc. All Rights Reserved. Visit Our Family of Brands Brands. OS Compatibility Checker. Please select your product to start. Pick your product by type Pick your product by range. Focusrite Plc; Anti-Slavery; Terms. As a user, installing the macFUSE software package will let you use any third-party FUSE file system. Legacy MacFUSE file systems are supported through the optional MacFUSE compatibility layer. As a developer, you can use the FUSE SDK to write numerous types of new file systems as regular user space programs. The original application compatibility table is still here, now with more than 8,000 apps in the database. Check if your favourite apps work with macOS Big Sur now. Specs: AMD FX-6200 3.8 GHz 6-core CPU G-Skill 16GB (2 x 8GB) DDR3-1833MHz GeForce GT 740 ASRock 970 Pro3 R2.0 Thanks:).

If you're using one of these computers with OS X Mavericks or later, you can install macOS Catalina. Your Mac also needs at least 4GB of memory and 12.5GB of available storage space, or up to 18.5GB of storage space when upgrading from OS X Yosemite or earlier. Learn how to upgrade to macOS Catalina.

MacBook Pro

MacBook Pro (13-inch, 2020, Two Thunderbolt 3 ports)
MacBook Pro (13-inch, 2020, Four Thunderbolt 3 ports)
MacBook Pro (16-inch, 2019)
MacBook Pro (13-inch, 2019, Two Thunderbolt 3 ports)
MacBook Pro (15-inch, 2019)
MacBook Pro (13-inch, 2019, Four Thunderbolt 3 ports)
MacBook Pro (15-inch, 2018)
MacBook Pro (13-inch, 2018, Four Thunderbolt 3 ports)
MacBook Pro (15-inch, 2017)
MacBook Pro (13-inch, 2017, Four Thunderbolt 3 ports)
MacBook Pro (13-inch, 2017, Two Thunderbolt 3 ports)
MacBook Pro (15-inch, 2016)

MacBook Pro (13-inch, 2016, Four Thunderbolt 3 ports)
MacBook Pro (13-inch, 2016, Two Thunderbolt 3 ports)
MacBook Pro (Retina, 15-inch, Mid 2015)
MacBook Pro (Retina, 15-inch, Mid 2015)
MacBook Pro (Retina, 13-inch, Early 2015)
MacBook Pro (Retina, 15-inch, Mid 2014)
MacBook Pro (Retina, 13-inch, Mid 2014)
MacBook Pro (Retina, 15-inch, Late 2013)
MacBook Pro (Retina, 15-inch, Early 2013)
MacBook Pro (Retina, 13-inch, Late 2013)
MacBook Pro (Retina, 13-inch, Early 2013)
MacBook Pro (Retina, 15-inch, Mid 2012)
MacBook Pro (15-inch, Mid 2012)
MacBook Pro (Retina, 13-inch, Late 2012)
MacBook Pro (13-inch, Mid 2012)

MacBook Air

MacBook Air (Retina, 13-inch, 2020)
MacBook Air (Retina, 13-inch, 2019)
MacBook Air (Retina, 13-inch, 2018)
MacBook Air (13-inch, 2017)
MacBook Air (13-inch, Early 2015)
MacBook Air (11-inch, Early 2015)

MacBook Air (13-inch, Early 2014)
MacBook Air (11-inch, Early 2014)
MacBook Air (13-inch, Mid 2013)
MacBook Air (11-inch, Mid 2013)
MacBook Air (13-inch, Mid 2012)
MacBook Air (11-inch, Mid 2012)

MacBook

MacBook (Retina, 12-inch, 2017)
MacBook (Retina, 12-inch, Early 2016)

iMac Pro

iMac

iMac (Retina 5K, 27-inch, 2020)
iMac (Retina 5K, 27-inch, 2019)
iMac (Retina 4K, 21.5-inch, 2019)
iMac (Retina 5K, 27-inch, 2017)
iMac (Retina 4K, 21.5-inch, 2017)
iMac (21.5-inch, 2017)
iMac (Retina 5K, 27-inch, Late 2015)
iMac (Retina 4K, 21.5-inch, Late 2015)
iMac (21.5-inch, Late 2015)

iMac (Retina 5K, 27-inch, Mid 2015)
iMac (Retina 5K, 27-inch, Late 2014)
iMac (21.5-inch, Mid 2014)
iMac (27-inch, Late 2013)
iMac (21.5-inch, Late 2013)
iMac (27-inch, Late 2012)
iMac (21.5-inch, Late 2012)

Mac mini

Mac Pro

A tool for checking backward API/ABI compatibility of a C/C++ library

ABI Compliance Checker (ABICC) is a tool for checking backward binary and source-level compatibility of a C/C++ library.

The tool analyzes changes in API/ABI (ABI=API+compiler ABI) that may break binary compatibility and/or source compatibility: changes in calling stack, v-table changes, removed symbols, renamed fields, etc.

The tool can create and compare ABI dumps for header files and shared objects of a library. The ABI dump for a library can also be created by the ABI Dumper tool if shared objects include debug-info.

Binary incompatibility may result in crashing or incorrect behavior of applications built with an old version of a library if they run on a new one. Source incompatibility may result in recompilation errors with a new library version. The tool is intended for developers of software libraries and Linux maintainers who are interested in ensuring backward compatibility, i.e. allow old applications to run or to be recompiled with newer library versions.

The tool is developed by Andrey Ponomarenko. You can order additional reports for visualization of the ABI structure and high detailed binary compatibility analysis here: https://abi-laboratory.pro/

The tool is a core of the ABI Tracker and Upstream Tracker projects.

Downloads

The latest release can be downloaded from this page.

Read-only access to the latest development version:

git clone https://github.com/lvc/abi-compliance-checker.git

License

This program is free software. You may use, redistribute and/or modify it under the terms of the GNU GPL or GNU LGPL

Supported Platforms

GNU/Linux, FreeBSD, Mac OS X, MS Windows.

Dependencies

Hackintosh compatibility checker download

G++ (3.0-4.7, 4.8.3 or newer)
GNU Binutils (readelf, c++filt, objdump)
Perl 5
Ctags

WARNING: if you are using ccache program (i.e. gcc points to /usr/lib/ccache/gcc) then it should be newer than 3.1.2 or disabled.

On Mac OS X the tool also requires Xcode (g++, c++filt, nm and otool).

On MS Windows the tool also requires MinGW, MS Visual C++ (dumpbin, undname, cl), Active Perl 5, adding of tool locations to the PATH and execution of vcvars64.bat script (C:Microsoft Visual Studio 9.0VCbin).

Installation

The tool is ready-to-use after extracting the archive.

You can also use a Makefile to install the tool into the system:

sudo make install prefix=PREFIX [/usr, /usr/local]

This command will install the abi-compliance-checker program into the PREFIX/bin system directory and private modules into the PREFIX/share.

To verify that the tool is installed correctly and it works on your host run:

cd tmp/

abi-compliance-checker -test

Usage with ABI Dumper

This new way is based on the analysis of the debug-info from binary objects. It's more reliable, faster and simple way.

The analyzed library should be compiled with '-g -Og' GCC options to contain DWARF debug info.

Create ABI dumps for both library versions first using the ABI Dumper tool:

abi-dumper OLD.so -o ABI-0.dump -lver 0

abi-dumper NEW.so -o ABI-1.dump -lver 1

And then compare ABI dumps to create report:

abi-compliance-checker -l NAME -old ABI-0.dump -new ABI-1.dump

The compatibility report will be generated to:

compat_reports/NAME/V0_to_V1/compat_report.html

Hackintosh Compatibility Checker Software

You can filter out private symbols from the ABI dumps by specifying of additional -public-headers option of the ABI Dumper tool.

Usage (Original)

The original usage is based on the analysis of header files and shared objects (without debug-info).

You should provide XML descriptors for two library versions (v1.xml and v2.xml files) in order to run the analysis. Library descriptor is a simple XML-file that specifies version number, paths to header files and shared libraries and other opti