Silverjuke is the easy-to-use jukebox with more than ten yeas of experience, see http://silverjuke.net for further information.

The Silverjuke source code is available under the GPL license, see the file LICENSE for details.

Linux/Unix: With chance, Silverjuke is available in your favorite packet manager. If it is not there, please contact your linux distributor - we cannot help on this point. Alternatively, more experienced users can build Silverjuke theirself. The source code from https://github.com/r10s/silverjuke plus a simple ./autogen.sh, make and make install should do the job. If you want to run silverjuke from your build dir, run ./silverjuke instead of make install.

Beyond the usual gcc and system development packages, chances are you'll also need the following, less common stuff:

• xine-devel
• wxWidgets-wxcontainer-devel

(note that your distro's default wxwidgets package might contain the stl version, which does not work with silverjuke. Check for something with wxcontainer in the name)

Windows: For Windows, an installation program with the most recent version is available at http://silverjuke.net . Note, that the windows binaries are not opened sourced.

Any issues can be reported to https://github.com/r10s/silverjuke/issues

Beside the possibility to code on the Silverjuke project itself, you can create skins (or maybe scripts) that will be loaded and executed by Silverjuke. For the possibilities on this, please refer to the docs folder.

If you want to code on Silverjuke yourself here are some hints that may be usefull esp. if you want to give your work back to the core (pull requests).

• For indentation we use tabs. Alignments that are not placed at the beginning of a line should be done with spaces.

• For padding between funktions, classes etc. we use 2 empty lines

• Files are encoded as UTF-8 with Unix-Lineends (a simple LF, 0x0A or \n)

• /sjbase contains the main functions and the startup routines

• /sjmodules does not contain loadable libraries but program parts that can communicate with message without knowing each other

• /sjtools contains - more or less - self-contained and independent classes and functions; there should be no references to /sjbase or /sjmodules

• the other directories are used libraries

• includes are done using the #include <dir/file.h> scheme which allows us to move files around and to "overwrite" files by include directories with a higher priority

If you use the Silverjuke source code as a base of your projects, keep in mind that Silverjuke is released under the GPL and you have to open source your work as well. See the file LICENSE that comes together with the source code.

Copyright (c) Bjoern Petersen Software Design and Development, http://b44t.com and contributors.