Downloading and Installing the Distribution

Installation Locations

The Installer program will let you choose a directory in which to place the binaries. If you are on a stand-alone machine, you should be logged in (or running Installer) as root and choose “/” for the installation directory (the default).

The frameworks and applications are installed into the appropriate platform locations given in Table 2.

Command line tools and manual pages will install into the /usr/local hierarchy on Unix type machines, specifically /usr/local/bin. Locations for command line Windows tools have yet to be determined.

If you are the system administrator for a NFS shared network, you probably want to choose a local directory which can be exported and create symbolic links into that directory on the networked machines. Alternatively, if you have a single server that exports /Local* and /usr/local, simply install the package there and you're done.

Building on GNUstep

On GNUstep systems, make is responsible for building the MusicKit sources. From the top level of the source tree, executing make should build Frameworks, Examples and Applications. Note that the applications and tools built may differ from the MacOS X set due to missing GNUmakefile definitions, but we aim to produce the same files on all platforms.

At the time of writing, GNUstep isn't able to build frameworks which depend on earlier built frameworks automatically. This requires installing each MusicKit framework individually, in order, in a similar fashion to the frameworks of GNUstep themselves. Also, the environment variables required by GNUstep for building must be defined while having root permissions in order to install. This is achieved with the following commands:

% ./configure
% sudo sh
# . /usr/GNUstep/System/Library/Makefiles/GNUstep.sh
# cd Frameworks/PlatformDependent/MKPerformSndMIDI_portaudio
# make install
# cd ../../SndKit
# make install
# cd ../MKDSP_Native
# make install
# cd ../MusicKit
# make install
# cd ../..
# make install

Building on MacOS X

On MacOS X, to benefit from the Xcode IDE (the IDE, plus zero-linking), make will just run the xcodebuild command line tool which does the actual building using the MusicKit.xcodeproj project. If configure determined some libraries were unavailable, they will be omitted from the CONFIGURED_LIBS variable passed on the command line when xcodebuild is run by make. Since xcodebuild install builds and then installs, the sudo make install suffices, typing a preceding make is not actually necessary.

The MusicKit project can also be built within the Xcode IDE GUI. However configure must be run before building with Xcode, in order to configure headers to selectively compile sources based on library availability. In addition, the default configuration is to assume if the Xcode GUI is being used, then the MusicKit is being developed, not just installed and that all libraries have been installed. If all of the libraries are not available, the build setting CONFIGURED_LIBS must be changed for the SndKit to remove those libraries which are not installed. In practice, the user must manually modify CONFIGURED_LIBS build setting in the SndKit target to match the setting in Makefile.

To build on MacOS 10.6, currently the MusicKit and SndKit frameworks must be built for the i386 32 bit architecture. This requires the supporting libraries to also be built as i386 binaries. Assuming the support libraries are built with an i386 architecture binary, configure needs to be instructed to test the library linking with the i386 architecture, using the -arch flag:

./configure CFLAGS="-arch i386"
make

The MKUnitGenerators and MKSynthPatches frameworks won't compile on platforms other than OpenStep or NeXTStep because the Motorola asm56000 and lnk56000 tools are missing.

Installing a MIDI driver

If necessary, compile and install an appropriate MIDI driver.

To compile the MacOS X-Server V1.2 Zilog SCC MIDI driver, some header files are missing. You can get them from the Darwin distribution of the SoundKit, copy them from a NeXTStep 3.3/OpenStep 4.2 system, or as a convience, they are made available for download.

MacOS X Developer release includes source for a generic USB MIDI driver at /Developer/Examples/CoreAudio/MIDI/SampleUSBDriver. There is also a driver binary for the MIDIMan MIDISPORT™ USB interfaces for MacOS X available for download from MIDIMan's web page and other vendors may well have drivers available for their hardware.