dnrops
/
osxfuse
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
219 Commits 4 Branches 116 Tags 1.7 MiB
Go to file
Benjamin Fleischer 532751da17 Clean up Homebrew instructions 2016-01-18 21:35:10 +01:00
framework@2ab904a30b (framework) Set st_size for directories 2015-01-08 01:02:24 +01:00
fuse@98b9960960 (fuse) Minior code cleanup 2014-03-12 22:35:20 +01:00
kext@6d927ab722 Bump version to 2.8.3 2016-01-18 20:08:34 +01:00
macfuse@f340bc4723 Create submodule for MacFUSE libosxfuse_i32/libosxfuse_i64 adapter 2012-02-27 03:23:05 +01:00
packaging Update copyright year in license 2016-01-18 08:23:39 +01:00
prefpane@4813708974 Bump version to 2.8.3 2016-01-18 20:08:34 +01:00
.gitignore Add file .gitignore 2011-06-21 09:09:27 +02:00
.gitmodules Create submodule for MacFUSE libosxfuse_i32/libosxfuse_i64 adapter 2012-02-27 03:23:05 +01:00
LICENSE.txt Update copyright year in license 2016-01-18 08:23:39 +01:00
README.md Clean up Homebrew instructions 2016-01-18 21:35:10 +01:00
build.sh Add support for Xcode 7.1 and update 7.0 2015-09-10 08:21:31 +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 backward compatible 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 locates automatically 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 as many versions of OS X as possible (depending on the versions of Xcode that are installed).

  • Xcode 3.1: FUSE for OS X can be built for Mac OS X 10.5.

  • Xcode 3.2: FUSE for OS X can be built for Mac OS X 10.5 to 10.8.

  • Xcode 4.0, 4.1, 4.2, 4.3: FUSE for OS X can be built for Mac OS X 10.6 to 10.8.

  • Xcode 4.4, 4.5, 4.6: FUSE for OS X can be built for OS X 10.7 and 10.8.

  • Xcode 5.0: FUSE for OS X can be built for OS X 10.8

  • Xcode 5.0.1, 5.1: FUSE for OS X can be built for OS X 10.8 to 10.11

  • Xcode 6.0, 6.1, 6.2, 6.3, 6.4: FUSE for OS X can be built for OS X 10.9 to 10.11

  • Xcode 7.0, 7.1: FUSE for OS X can be built for OS X 10.11

Note:

  • 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).

  • Xcode 3.1 is supported to allow native building under Mac OS X 10.5, but the "dist" and "smalldist" targets don't work there due to the lack of the pkgbuild tool. Other targets work.

  • Mavericks (and maybe Yosemite?) users: Beware that Apple introduced a new version of /usr/bin/lipo in Jan 2014 which is incompatible with older Xcode versions. If your build hangs running /usr/bin/lipo (with "top" showing a constant lipo/xcrun bounce), you need to replace it with a working version. The Sep 2012 version from Mountain Lion is known to work, as is the May 2014 version from MacPorts.

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-2 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 dist