iTunesFS has come a long way since its first inception in 2007. It linked against MacFUSE and was developed on a G5 Power Mac running OSX 10.4.x using Xcode 2.x in a couple of days. Later, I got an Intel Mac and subsequently added Intel support to iTunesFS. In the meantime, MacFUSE was abandoned and other projects took over, with macFUSE (then called OSXFUSE) prevailing. Also, Apple dropped the PowerPC platform and recent Xcode versions lost their backwards compatibility for older SDKs (usually only supporting the previous platform SDK). At the time of writing (September 2016) Xcode 8 and macOS 10.12 were just released - and iTunesFS still has backwards compatibility up to OSX 10.5/PowerPC!
You have to install macFUSE. macFUSE provides a framework and headers that iTunesFS uses.
You need to get a recent Xcode from
Apple's developer site in order to compile
iTunesFS on OSX / macOS.
There are 2 shared schemes for building iTunesFS, Debug
and Release
.
Both schemes are based on their respective
xcconfig
files debug and release
which both include a common base.
Debug
will build a debug version for the current SDK and architecture, only. This will work out of the box on all machines (tell me if it doesn't!)Release
will build a release version for several SDKs (including SDKs you won't have on your machine!) andi386
andppc
architectures (the latter your Xcode won't probably support!)
In order to fix Release
you have two options:
- edit
release.xcconfig
and addVALID_ARCHS = $(NATIVE_ARCH_ACTUAL)
andARCHS = $(NATIVE_ARCH_ACTUAL)
anywhere. Of course you can also provide any other value which will work in your development environment. - modify Xcode to provide backwards compatibility for old SDKs, compilers and linkers. That's what I have done myself, but I can't release such a project publicly due to the SDKs and old binaries being copyrighted by Apple.