2ab560d029
* (framework) Use OSXFUSE logo as default volume icon * (kext) Fix length of FUSE_WRITE message in strategy operation Closes issue #28: Bad length passed to client process in write operation * (kext) Finish ticket reference counting * (kext) Do not wait for an answer, if we are not interested in the result * (kext) Fix race condition in fticket_aw_pull_uio (FT_A_BUF) * (framework) Fix header search path * (prefpane) Fix path of kernel extension * (prefpane) Fix path of preferences file |
||
---|---|---|
framework@5ede69f330 | ||
fuse@887598e045 | ||
kext@9630fc84bd | ||
macfuse@f340bc4723 | ||
packaging | ||
prefpane@5b25b8e727 | ||
.gitignore | ||
.gitmodules | ||
LICENSE.txt | ||
README.md | ||
build.sh |
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).
- Building OSXFUSE on Mac OS X 10.6:
- Building OSXFUSE for Mac OS X 10.5 requires Xcode 3.2
- Building OSXFUSE for Mac OS X 10.6 and later requires Xcode 3.2 or 4.0
- Building OSXFUSE on Mac OS X 10.7:
- Building OSXFUSE for Mac OS X 10.5 requires Xcode 3.2
- Building OSXFUSE for Mac OS X 10.6 and later requires Xcode 3.2, 4.1, 4.2 or 4.3
Note:
-
Xcode 4.3 does no longer include Autotools (
aclocal
,autoconf
,autoheader
,automake
,autoreconf
) and Libtool (glibtoolize
), that are needed to buildlibosxfuse
. 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 in 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 ingen_bridge_metadata
(hard coded path tocpp
).
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.4 git://github.com/osxfuse/osxfuse.git osxfuse
Run the following command in the cloned repository to build OSXFUSE from source:
./build.sh -t dist