dnrops
/
osxfuse
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
331 Commits 4 Branches 116 Tags 1.7 MiB
Go to file
Benjamin Fleischer 5cccd3a38a Remove obsolete Git submodules 2016-02-15 23:48:01 +01:00
build.d Drop MacFUSE compatibility layer 2016-02-15 22:30:12 +01:00
common Drop MacFUSE compatibility layer 2016-02-15 22:30:12 +01:00
framework@b5d552d5e6 (framework, kext) Clean up preprocessor macros 2015-05-15 18:09:13 +02:00
fuse@b0dddb6871 (fuse) Remove deprecated functions 2016-02-15 23:41:52 +01:00
kext@06cc3c5765 Drop MacFUSE compatibility layer 2016-02-15 22:30:12 +01:00
prefpane@a135b78458 (prefpane) Use HTTPS to fetch list of releases 2015-09-08 23:13:54 +02:00
support@375186233d Drop MacFUSE compatibility layer 2016-02-15 22:30:12 +01:00
.gitignore Add file .gitignore 2011-06-21 09:09:27 +02:00
.gitmodules Remove obsolete Git submodules 2016-02-15 23:48:01 +01:00
LICENSE.txt Update copyright year in license 2016-01-17 18:07:55 +01:00
README.md Drop MacFUSE compatibility layer 2016-02-15 22:30:12 +01:00
build.sh (build) Hide xcodebuild output if verbose not set 2015-09-02 17:26:13 +02:00

README.md

FUSE for OS X

FUSE for OS X allows you to extend Mac OS X via third party file systems.

About FUSE for OS X

The FUSE for OS X software package provides multiple APIs for developing file systems for Mac OS X 10.5 to 10.11 (Intel and PowerPC architecture). It is a successor to MacFUSE, which has been the basis of many products, but is no longer being maintained.

You can use the provided APIs to develop numerous types of file systems, whose content can come from a local disk, from across the network, from memory, or any other source. One of these APIs is a superset of the FUSE API, that originated on Linux.

Due to the fact that FUSE file systems are regular applications (as opposed to kernel extensions), you have just as much flexibility and choice in programming tools, debuggers, and libraries as you have if you were developing standard Mac OS X applications.

For more information visit the website of the FUSE for OS X Project.

Build Instructions

The build script automatically locates all supported installations of Xcode in the top level of the Mac OS X startup volume and the Applications folder. It builds a distribution package compatible with the currently running version of OS X.

Note:

  • On Mac OS X 10.6 Xcode versions 4.0, 4.1, and 4.2 are not supported due to a bug in Xcode's linker. Use Xcode 3.2.6 to build FUSE for OS X. See "Fun with weak dynamic linking" for more details.

  • Xcode 4.3 and newer versions do not include autotools and libtool, that are needed to build libosxfuse. Install MacPorts or Homebrew and run the following commands in Terminal to install the required tools:

MacPorts:

    sudo port install autoconf automake libtool gettext

Homebrew:

    brew install autoconf automake libtool gettext
    brew link --force gettext
  • The "Command Line Tools" package is needed to generate BridgeSupport metadata for OSXFUSE.framework because of a bug in gen_bridge_metadata (hard coded path to cpp).

The Xcode tools packages can be obtained from https://developer.apple.com/downloads/ (free Apple Developer ID required).

To clone the source repository into a newly created subdirectory named osxfuse in the current working directory, run the following command in Terminal:

git clone --recursive -b support/osxfuse-3 git://github.com/osxfuse/osxfuse.git osxfuse

Run the following command in the cloned repository to build FUSE for OS X from source:

./build.sh -t distribution

The resulting distribution package can be found in /tmp/osxfuse/distribution.