How to build a project using MixDown

1. Run MixDown in import mode with the locations of all of the packages that you expect to be needed in to properly build the desired project. For example to import subversion, run the following command:

mixdown --import http://www.eng.lsu.edu/mirrors/apache/apr/apr-1.3.12.tar.bz2 apr-util-1.3.10.tar.bz2 neon-0.29.5.tar.gz sqlite-autoconf-3070500.tar.gz subversion-1.6.12.tar.bz2

MixDown will then download, unpack, and analyze all of the given packages for their respective build systems and their dependencies. Unless they use non-standard build systems, MixDown can properly detect how they depend on each other and if you might require more packages. If you run MixDown in interactive mode (command-line option), you can tell it where to get the new dependancies. Otherwise MixDown will just list them as possible dependencies to stdout.

In this example, subversion-1.6.12.md will be generated. This is MixDown's project file. Inside of it will be everything that MixDown needs to know on how to build the given packages. You can hand-edit this file if something was not quite right. For more information, see Projects.

2. Build targets by running MixDown on the created project file in build mode (default mode). The following command will run with 4 job slot, verbose mode, and install to location 'TestPrefix':

mixdown -j4 -v -pTestPrefix subversion-1.6.12.md

For more information on command line options, read Command Line Options.

4. (Optional) Clean targets by running MixDown in clean mode with the following command:

mixdown --clean subversion-1.6.12.md