Fulltext results:
- 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
- automated_build_system
- releases for the project. ===== Overview ===== Doomsday's automated build system has been set up for dail... ailable in [[https://launchpad.net/~sjke/+archive/doomsday|skyjake's PPA]]. On other operating systems, you... en tagged in the Git repository; you can check it out and build as you see fit. ==== Build numbers ==... he build number for March 7, 2011 is 66. When the Doomsday version number is incremented, the build number w
- libcore
- he shared library that contains the core of the [[doomsday_engine]] version 2.((The actual file name depends... ore.so**.)) It is based on [[hawthorn]]. ====== Doomsday 2 architecture ====== Doomsday 2 comprises a set of libraries that act as the foundation of [[doomsday_client]], Server, [[shell]], and other applicatio
- compiling_and_running_2.0
- //dengine.net/source|source package]]. * Check out the [[https://github.com/skyjake/Doomsday-Engine|Doomsday-Engine]] repository from GitHub: <code bash>git clone --recursive https://github.com/skyjake/Doomsday-Engine</code> You can then switch to any release ... gin) * FMOD Studio Low-Level Programmer API for Doomsday 2.1+, or FMOD Ex for Doomsday 2.0 or earlier (audio plugin) * OpenAL (audio plugin) * libXrandr and li
- release_packaging
- need to check out the appropriate version/branch out of the deng [[svn_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... Linux, Unix, Mac OS X ====== In Unix-like OSes, Doomsday is compiled with [[http://www.cmake.org|CMake]]. ... ry you've created yourself. For example: $ **cd doomsday** $ **mkdir mybuild** $ **ccmake ..** $ **m
- compilation_fedora_22
- ng a clean installation of Fedora Workstation 22, Doomsday can be checked out, built, and installed with the following commands... it clone --recursive ssh://git@github.com/skyjake/Doomsday-Engine.git deng $ mkdir deng/build $ cd deng/buil... ILD_TYPE=Release -DPREFIX=${my_install_prefix} ../doomsday $ make $ make install </code> ===== Qt5OpenGLExt
- directory_structure
- such things as bringing some consistency into the Doomsday source directory structure. I think the following... lude/ (engine's internal files) api/ (doomsday.h, dd_share.h, doomsday.def, etc.) defs/ (engine's definition files) plugins/ jdoom/ (the ... inition files being under Defs/jHeretic. * The Doomsday [[public_api]] can be separated cleanly into its
- fluid_synth_plugin
- , look for the "Audio configuration" printed in [[doomsday.out]]. It should contain a mention of FluidSynth bein... th synthesizer that outputs PCM sample data using Doomsday's main SFX interface. In this mode, FluidSynth do
- player_controls
- this works in the client/server architecture that Doomsday is using. ===== Motivation ===== Why are play... control of a specific player. These are composed out of multiple sources of data, i.e., all the device... == Goal N+1: Player Control Setup GUI ==== * Doomsday control panel UI for setting up the controls.
- file_system
- e ''de::FS'' class is the main interface to the [[Doomsday 2]] internal file system. It maintains a tree of ... s are responsible for deciding when instances get out-of-date and need to be deleted (pruning). Pruning
- ui_framework
- The Doomsday 2 [[ui_framework]] was first introduced in [[version_1.11]]. To the end user it provides an an... nd supporting functionality for tasks like laying out and drawing text. ====== See also ====== *