Trouble building on macOS Sequoia 15.6, Xcode 16.4, fuse-t 1.0.49

[simX]

I'm trying to build fusehfs with fuse-t on macOS Sequoia 15.6, using Xcode 16.4 and with fuse-t 1.0.49 installed. I have a MacBook Air M1. I'm having some trouble. I was able to get it to build the .fs filesystem bundle in the end, but when installing it to /Library/Filesystems, HFS .img files don't mount consistently in the Finder and I sometimes get errors saying that it couldn't mount.

I installed fuse-t 1.0.49 with homebrew: brew install fuse-t. I downloaded this repository, and changed the location of libfuse-t-1.0.34.dylib to libfuse-t-1.0.49.dylib in the same directory. But when trying to build, I still get a 'fuse/fuse.h' file not found error for fusefs_hfs.c, line 23: #include <fuse/fuse.h> when building the mount_fusefs_hfs target. No matter what I put in any of the header search paths (I tried to add /Library/Application Support/fuse-t/include/fuse) in all of the various config build settings of the project file or the mount_fusefs_hfs target itself, I couldn't ever get Xcode to find the proper header files for some reason.

Eventually I just coped the header files from /Library/Application Support/fuse-t/include/fuse into the project itself and then changed fusefs_hfs.c line 23 to #include "fuse.h" which is definitely the wrong approach but it at least allowed it to build.

I'm also still getting some errors when building the hfsutils target that I can't seem to figure out how to fix:

autoreconf: warning: autoconf input should be named 'configure.ac', not 'configure.in'
Can't exec "aclocal": No such file or directory at /opt/homebrew/Cellar/autoconf/2.72/share/autoconf/Autom4te/FileUtils.pm line 299.
autoreconf: error: aclocal failed with exit status: 2

In any case, even with my hack getting the .fs bundle to build, double-clicking .img files doesn't consistently work. Sometimes it works fine. Sometimes the disk image mounts and also gives an error saying the .img failed to mount. And sometimes it fails silently. I don't seem to see any log files in the Console.

I'm certainly doing something wrong but I'm not sure what.