This shows you the differences between two versions of the page.
— | devel:release_packaging [2011-03-06 16:36] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | {{update}} | ||
+ | |||
+ | This article explains the process used for creating release packages of the [[doomsday_engine]] on various platforms. | ||
+ | |||
+ | To create a release, you will need to check out the appropriate version/ | ||
+ | |||
+ | |||
+ | ====== Windows ====== | ||
+ | |||
+ | |||
+ | < | ||
+ | </ | ||
+ | This batch file will package Snowberry, rebuild the PK3s, recompile Doomsday and all the plugins, and finally create an Inno Setup installer into the **packages** subfolder. Note that the script assumes you have Inno Setup 5 installed in **C: | ||
+ | |||
+ | |||
+ | ====== Linux, Unix, Mac OS X ====== | ||
+ | |||
+ | |||
+ | In Unix-like OSes, Doomsday is compiled with [[http:// | ||
+ | |||
+ | * You should run cmake within an empty directory you've created yourself. For example: | ||
+ | $ **cd doomsday** | ||
+ | $ **mkdir mybuild** | ||
+ | $ **ccmake ..** | ||
+ | $ **make** | ||
+ | * In the Snowberry root folder, run the **macbuild.sh** script, specifying the version of the release package. | ||
+ | $ **./ | ||
+ | |||
+ | This will result in a compressed disk image being written to the **images** subfolder. | ||
+ | |||
+ | NOTE: Check the **macbuild.sh** script for the location where the application bundles are copied from. By default it is **doomsday/ | ||
+ | |||
+ | |||
+ | ====== SourceForge File Releases ====== | ||
+ | |||
+ | |||
+ | Team members will upload the new release to SourceForge.net file release system. | ||
+ | |||
+ | |||