v2.1.2

What's New in v2.1.2

New platforms

• Linux ARM64 binary now shipped (via matrix build on ubuntu-22.04-arm).
• macOS Apple Silicon + Intel binaries are now built separately (macos-15 matrix), instead of a single universal-ish artifact.

Build & toolchain modernization

• Code requires C++17, CMake 3.16+, Boost 1.71+.
• Legacy Intel TBB support removed — oneTBB is now required.
• gemmi bumped 0.6.6 → 0.7.5 (now compiles src/symmetry.cpp since 0.7+ is no longer fully header-only).
• Modernized Eigen, xxHash and math constants usage.
• common_utils submodule removed; sources inlined into src/utils/.

Wider glibc compatibility

• New LEGACY_GLIBC_EXP CMake option (x86_64 Linux only) pins libm exp() to its GLIBC_2.2.5 symbol via a wrap shim, letting the shipped binary load on RHEL 8, Ubuntu 18.04, Debian 10, openSUSE Leap 15.x and other pre-glibc-2.29 hosts. The official
  release tarball for x86_64 Linux uses this; arm64 is unaffected.

Snap

• Rebased on core24 (Ubuntu 24.04 base, boost 1.83, glibc 2.39).
• Compiled with -march=sandybridge for broad CPU compatibility (any AVX-capable x86_64 from 2011 onward), -O3 -flto=auto for performance.
• arm64 snap also shipped (-march=armv8-a).
• Now builds reproducibly inside a clean container — no host-toolchain leakage.

Bug fixes

• Windows: fixed a sharing-violation crash when supercell tries to delete stale output files between runs.

CI / quality

• Added a regression suite that runs the six tutorial cases against the previously published binary on every push and fails the build if output diverges. Helps catch silent numerical drift across compiler/dependency changes.
• macOS, Linux and Windows builds all gated on the same output-equivalence check.

Full changelog: v2.1.1...v2.1.2

v2.1.1

What's Changed

• Updated external deps, minor bugfixes, obsolete code removed. by @orex in #66

Full Changelog: v2.1.0...v2.1.1

Version 2.1.0

New version with improved electrostatic precision and multi threading performance.

New major release of supercell program

v2.0.1

Fix issue #37