DerMixD employs a build system based on one Makefile for GNU Make. There is a frontend configure script to give you the usual scheme of

	./configure && make && make install

to configure and execute the build and then install the result in appropriate places. Feel free to query

	./configure --help

or

	make help

for detailed instructions. The latter will, at the first time, work a bit to generate the dependency files. You can prevent that (for the 'help' target unnecessary) step via

	make DRY_RUN=yes help

I encourage use of GNU Make's parallel build feature by providing the number of jobs with the -j parameter. If you happen to start hacking on DerMixD, you should not need to hack the Makefile itself unless for adding libraries, as long as you follow the conventions that hopefully are apparent in the code layout. Build rules are regenerated from the present .hxx/.cxx files automatically.

Of course there are prerequisites to fulfill before having fun with DerMixD. Here we go!

Hard dependencies:

	* POSIX system C++ compiler, POSIX thread library
	* GNU Make for build (version 3.81 tested)
	* Perl 5 for build system and frontend scripts

Optional dependencies:
	* Audio format libraries:
		- libmpg123
		- libsndfile
		- libvorbisfile
	* Audio output libraries/headers:
		- ALSA's libasound
		- OSS
	* LADSPA header for LADSPA plugin support
	* SoundTouch (soundtouch-1.4) for time stretching effect
	* libmagic from file >= 5 for better file type detection

For frontend scripts only:
	* Config::Param Perl library (available via CPAN)

The generated dependencies are located in files under .deps/ and are also depending on the fixed build configuration (the file config.mk being generated by make on the first run, or the configure wrapper script). The allclean target removes that directory, too.
