Skip to content

Commit

Permalink
hfsfuse: Use unprefixed FUSE header for compatibility
Browse files Browse the repository at this point in the history
More systems support this out of the box, and those that don't can
be handled by adding to the include path, while the inverse is not true.

This is also the expected header when using pkg-config to discover FUSE,
though we don't do this currently, and not all systems that break from
this convention ship with a fuse.pc.
  • Loading branch information
0x09 committed Jan 23, 2021
1 parent c7e10ea commit 8e09fb6
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ ifeq ($(OS), Darwin)
else ifeq ($(OS), Haiku)
CFLAGS += -D_BSD_SOURCE
APP_LIB += -lbsd
FUSE_FLAGS += -I/system/develop/headers/userlandfs -I/system/develop/headers/bsd
FUSE_FLAGS += -I/system/develop/headers/userlandfs/fuse -I/system/develop/headers/bsd
FUSE_LIB = -L/system/lib/ -luserlandfs_fuse
PREFIX ?= /boot/home/config/non-packaged
else ifeq ($(OS), FreeBSD)
Expand Down
2 changes: 1 addition & 1 deletion src/hfsfuse.c
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@
#include <errno.h>
#include <limits.h>
#include <inttypes.h>
#include <fuse/fuse.h>
#include <fuse.h>

#ifndef HFSFUSE_VERSION_STRING
#include "version.h"
Expand Down

0 comments on commit 8e09fb6

Please sign in to comment.