Announcing macFUSE 4.10.0

Announcing macFUSE 4.10.0 Posted on 08 Mar 2025

Download macFUSE 4.10.0 macOS 10.9 to 15 Apple Silicon or Intel SHA-256: 6a532aa102325efdb727fd85ed677b6d07c652d88398f031acaf0cfc3b359645

Add experimental support for libfuse3

Some macOS specific features require FUSE API extensions that break compatibility with the vanilla FUSE API. Setting the compile-time flag FUSE_DARWIN_ENABLE_EXTENSIONS to 0, when building a file system, disables those API extensions. By default, the macOS specific API extensions are enabled.

Please note:
- macFUSE 4.10.0 supports FUSE ABI version 7.19 and includes patched versions of libfuse 2.9.9 and libfuse3 3.17.1 RC1.
- The macOS specific libfuse3 API might not be stable, yet. This means that libfuse3 file systems that are built for macFUSE 4.10.0 might need to be updated to work with future macFUSE releases.
Use iconv() instead of CFStringNormalize() to normalize file names in the high level FUSE API. Calling CFStringNormalize() after daemonizing the file system process results in a crash. See File Names (Unicode Normalization Forms) for details on file name normalization.
Work around a limitation preventing a single process from mounting multiple GMUserFileSystems (macFUSE.framework) at the same time. Even though a single process can mount multiple GMUserFileSystems, it is recommended to use a separate process per virtual volume. For details, see macfuse/macfuse#1059.
Do not delete intermediate Xcode build files after building a target
Fix a build script logging bug when cleaning a build target