Advanced builds

The 86Box Jenkins provides all kinds of pre-release testing builds for advanced users. These are linked to the 86Box git repository on GitHub; a new build is produced with the latest source code every time the repository is updated.

Important

Testing builds are development snapshots which may contain bugs, incomplete features or other issues. These should only be used if you know what you’re doing.

Standard

Standard builds (86Box) are compiled with default options. Release versions of 86Box are based on standard builds.

Debug

Debug builds (86Box-Debug) are standard builds compiled with debug symbols and no optimizations, to allow for debugging with gdb and other tools if you don’t have a full 86Box development setup. Debug builds run slower than standard builds due to the removal of optimizations and addition of debugging features.

Development

Development builds (86Box-Dev) are compiled with DEV_BUILD=y, enabling additional features which are currently under development. These new features might not work, either partially or entirely, and the development team reserves the right to change or remove them at any time.

Optimized

Optimized builds (86Box-Optimized) are standard builds which have been optimized for use with a specific CPU family on the host machine. Optimized builds provide slight performance improvements, especially on older or low-end hosts; however, the aggressive optimizations employed may result in bugs not present on standard builds.

There are many different optimized binaries available for each build, with each one corresponding to a CPU family. The table below lists most CPUs currently supported by optimized builds, along with the respective binaries you should use with them, as well as their codenames (as shown on an identification tool such as CPU-Z).

Note

Using the wrong optimized binary for your CPU will result in poor performance and/or crashes.

BinaryCPUsCodenames
Intel
Core2Core 2 Duo/Quad
Pentium Dual-Core
Conroe, Allendale, Merom,
Kentsfield, Wolfdale, Yorkfield
Nehalem1st generation CoreBloomfield, Lynnfield, Gulftown,
Arrandale, Clarkdale, Clarksfield
SandyBridge2nd/3rd generation CoreSandy Bridge, Ivy Bridge
Haswell4th/5th generation CoreHaswell, Broadwell
Skylake6th/7th/8th/9th/10th generation CoreSkylake, Kaby Lake, Coffee Lake,
Whiskey Lake, Amber Lake, Comet Lake
IceLake10th/11th generation CoreIce Lake, Tiger Lake, Rocket Lake
BonnellAtom (2008-2012)Silverthorne, Diamondville, Lincroft,
Pineview, Cedar Trail, Cover Trail
SilvermontAtom (2013+)Bay Trail, Cherry Trail, Braswell
N/J-series Celeron/PentiumBay Trail, Braswell, Apollo Lake,
Gemini Lake, Skyhawk Lake
AMD
K8 *All (2005-2007)
K10All (2008-2010)
BobcatAthlon (2011+)
FX
A/C/E-Series APU
Ontario, Zacate, Hondo, Llano, Trinity,
Richland, Kabini, Kaveri, Beema, Mullins,
Carrizo, Bristol Ridge, Stoney Ridge
ZenRyzen 1000/2000 CPU
Ryzen 2000/3000 APU **
Summit Ridge, Raven Ridge, Dali,
Pinnacle Ridge, Picasso
Ryzen Threadripper 1000/2000Whitehaven, Colfax
Zen2Ryzen 3000 CPU
Ryzen 4000 APU **
Ryzen 5000 CPU
Matisse, Renoir, Vermeer
Ryzen Threadripper 3000Castle Peak
* Older K8 CPUs without SSE3 are not supported.
** Ryzen APU = models equipped with integrated graphics, including G-series on desktop and U/H-series on mobile, which use older cores than the CPUs of the same series.