Building binary packages
Most users prefer binary packages for their platform instead of compiling the source code from the source tarball. This document is a collection of hints and cooking recipes dealing with building these packages for the various supported platforms.
If you build a binary package, please consider the following items:
- Linux packages should not contain any additional dependencies (aka libraries). Instead they should list these dependencies as requirements and let the package manager software do the rest.
- The Windows installer package should contain everything needed to run CRRCsim, including all DLLs (like SDL.dll). These libraries should be installed in the CRRCsim directory, not in a generic directory like Windows\System32. Only DLPortIO may not be included due to licensing issues.
- Documentation from the source tarball should be included in the binary packages or distributed as a separate package (crrcsim-doc). The CRRCsim package should recommend the installation of this doc-package if the package manager offers this feature.
- License information (a copy of the GPL) and other informational non-source text files must be included in the package.