Amendment to https://github.com/winfsp/cgofuse/pull/73
Now, FUSE-T headers should (always) be in /usr/local/include/fuse.
Previously, they could (sometimes) end up in /usr/local/include which didn't require specifying the path for most compilers.
As an aside, the Go tests on macOS fail with FUSE-T, but programs built with this branch (the examples and external projects) have been working in practice.
Not sure why that's the case.
Amendment to https://github.com/winfsp/cgofuse/pull/73 Now, FUSE-T headers should (always) be in
/usr/local/include/fuse
. Previously, they could (sometimes) end up in/usr/local/include
which didn't require specifying the path for most compilers.As an aside, the Go tests on macOS fail with FUSE-T, but programs built with this branch (the examples and external projects) have been working in practice. Not sure why that's the case.