dnrops
/
osxfuse
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
130 Commits 4 Branches 116 Tags 1.7 MiB
Go to file
Benjamin Fleischer 8e77a1b55d Bump version to 2.5.1 2012-08-10 22:47:47 +02:00
framework@4c22d1672e Bump version to 2.5.0 2012-07-31 23:42:52 +02:00
fuse@131ab62bbd Bump version to 2.5.0 2012-07-31 23:42:52 +02:00
kext@890b88a619 Bump version to 2.5.1 2012-08-10 22:47:47 +02:00
macfuse@f340bc4723 Create submodule for MacFUSE libosxfuse_i32/libosxfuse_i64 adapter 2012-02-27 03:23:05 +01:00
packaging Make sure that /usr/local/lib and /usr/local/include are readable 2012-06-03 00:02:27 +02:00
prefpane@8e34a96487 Bump version to 2.5.1 2012-08-10 22:47:47 +02: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 in licence 2012-04-11 01:33:40 +02:00
README.md Bump version to 2.5.0 2012-07-31 23:42:52 +02:00
build.sh Bump version to 2.5.1 2012-08-10 22:47:47 +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 OSXFUSE

The OSXFUSE software package provides multiple APIs for developing file systems for Mac OS X 10.5, 10.6 and 10.7 (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 OSXFUSE 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 OSXFUSE 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 Mac OS X as possible (depending on the versions of Xcode that are installed).

  • Xcode 3.2: OSXFUSE can be built with support for Mac OS X 10.5 and later versions.

  • Xcode 4.0, 4.1, 4.2, 4.3: OSXFUSE can be built with support for Mac OS X 10.6 and later versions.

  • Xcode 4.4: OSXFUSE can be built with support for OS X 10.7 and 10.8.

Note:

  • Xcode 4.3 and later versions do not include autotools and libtool, that are needed to build libosxfuse. Install MacPorts and run the following command in Terminal to install the required tools, if the build fails:

      sudo port install autoconf automake libtool

  • PackageMaker.app has been moved to the "Auxiliary Tools for Xcode" package starting with Xcode 4.3 and has to be installed separably.

  • The "Command Line Tools for Xcode" 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 at http://connect.apple.com (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 osxfuse-2 git://github.com/osxfuse/osxfuse.git osxfuse

Run the following command in the cloned repository to build OSXFUSE from source:

./build.sh -t dist