Fulltext results:
- automated_build_system
- d). ===== Scripts ===== The main build system scripts are part of the [[git_repository|Doomsday Git repository]]. ==== platform_release.py ==== //distrib/platform_release.py// is a script that detects the operating system and runs the appropriate build scripts to generate an installable binary distribution package under //distrib/releases//. The script takes no arguments. ==== autobuild.py ==== //
- compiling_and_running_1.15_or_earlier_qmake
- e "postbuild" subproject will automatically run a script that collects all the binaries into a single **Doomsday.app** bundle. Consequently, it is not necessary t... the game without "make install". ===== Running Doomsday under Qt Creator ===== ==== Windows ==== - G... un configuration. - Set **distrib\products\bin\doomsday.exe** as the executable. - Set the arguments, ... ==== Mac OS X ==== - Set **%{buildDir}/client/Doomsday.app** as the executable. - Add options as foll
- libcore
- ed_library]] * [[internal_file_system]] * [[doomsday_script]] * [[plugin_factory]] * [[packaging_resour
- developer_guidelines
- ====== Developer guidelines ====== Doomsday Engine is a diverse project that is free and open-source. As such, one of many ways to give back to Doomsday is by contributing code. Be it a bugfix, new fea... re, or even just cleanup, your work can help make Doomsday the most technically advanced Doom engine availab... pecially one with a large amount of code, such as Doomsday or the Linux kernel, it is imperative that there
- directory_structure
- such things as bringing some consistency into the Doomsday source directory structure. I think the following... lt binaries) win32/ (windows projects and scripts) mac/ (Xcode project) unix/ (Unix/Linux build scripts) engine/ scripts/ (engine scripts: makedmt.py) src/ include/ (engine's internal files)
- release_packaging
- ocess used for creating release packages of the [[doomsday_engine]] on various platforms. To create a relea... vn_repository]]. At a minimum, the **distrib**, **doomsday** and **snowberry** directories are needed. ===... ll package Snowberry, rebuild the PK3s, recompile Doomsday and all the plugins, and finally create an Inno S... er into the **packages** subfolder. Note that the script assumes you have Inno Setup 5 installed in **C:\P
- quick_guide_to_amethyst
- e. The Amethyst source code is included in the Doomsday Engine Git repository: http://github.com/skyjake/Doomsday-Engine/tree/master/doomsday/tools/amethyst ===== Installation ===== Even though Amethyst is part of the Doomsday //tools// subdirectory, it can be built independe
- compiling_and_running_3.0
- ctions ===== - Clone the repository. - Run ''doomsday/build/scripts/build_deps.py build'' to download and compile th
- file_system
- e ''de::FS'' class is the main interface to the [[Doomsday 2]] internal file system. It maintains a tree of ... engine's internal state, including configuration scripts, UI objects, the game world and its objects, and
- libdeng2_code_guidelines
- izes the coding conventions and practices used in Doomsday 2.0 (libdeng2 library). * more modular: core,... eed to include both function name and the error description (without a period in the end) -- see the exist