1 Sauerbraten source code license, usage, and documentation.
\r
3 You may use the sauerbraten source code if you abide by the ZLIB license
\r
4 http://www.opensource.org/licenses/zlib-license.php
\r
5 (very similar to the BSD license):
\r
11 Sauerbraten game engine source code, any release.
\r
13 Copyright (C) 2001-2006 Wouter van Oortmerssen.
\r
15 This software is provided 'as-is', without any express or implied
\r
16 warranty. In no event will the authors be held liable for any damages
\r
17 arising from the use of this software.
\r
19 Permission is granted to anyone to use this software for any purpose,
\r
20 including commercial applications, and to alter it and redistribute it
\r
21 freely, subject to the following restrictions:
\r
23 1. The origin of this software must not be misrepresented; you must not
\r
24 claim that you wrote the original software. If you use this software
\r
25 in a product, an acknowledgment in the product documentation would be
\r
26 appreciated but is not required.
\r
27 2. Altered source versions must be plainly marked as such, and must not be
\r
28 misrepresented as being the original software.
\r
29 3. This notice may not be removed or altered from any source distribution.
\r
34 The license covers the source code found in the "src" directory of this
\r
35 archive, the included enet network library which sauerbraten uses is covered by
\r
36 an MIT-style license, which is however compatible with the above license for all
\r
39 Game media included in the game (maps, textures, sounds, models etc.)
\r
40 are NOT covered by this license, and may have individual copyrights and
\r
41 distribution restrictions (see individual readmes).
\r
46 Compiling the sources should be straight forward.
\r
48 Unix users need to make sure to have the development version of all libs
\r
49 installed (OpenGL, SDL, SDL_Mixer, SDL_Image, zlib, libpng). The included
\r
50 makefiles can be used to build.
\r
52 Windows users can use the included visual studio .net project files, which
\r
53 references the lib/include directories for the external libraries and should
\r
54 thus be self contained. Release mode builds will place executables in the bin dir
\r
55 ready for testing and distribution. Do not come ask me for help in compiling
\r
56 or modifying the sources, if you can't figure out how to do this yourself
\r
57 you probably shouldn't be touching the files anyway.
\r
59 An alternative to visual studio for Windows is MinGW. In order to compile
\r
60 using MinGW, copy Makefile.mingw from the mingw directory to the src directory.
\r
61 You can also optionally copy make.mingw.bat to the sauerbraten directory for an
\r
62 easy way to compile.
\r
64 The sauerbraten sources are very small, compact, and non redundant, so anyone
\r
65 wishing to modify the source code should be able to gain an overview of
\r
66 sauerbraten's inner workings by simply reading through the source code in its
\r
67 entirety. Small amounts of comments should guide you through the more
\r
70 When reading the source code and trying to understand sauerbaten's internal design,
\r
71 keep in mind the goal of cube: minimalism. I wanted to create a very complete
\r
72 game / game engine with absolutely minimal means, and made a sport out of it
\r
73 keeping the implementation small and simple. Sauerbraten is not a commercial product,
\r
74 it is merely the author's idea of a fun little programming project.
\r
79 Wouter van Oortmerssen aka Aardappel
\r
83 For additional authors/contributors, see the sauerbraten binary distribution readme.
\r