Fulltext results:
- compiling_and_running_1.15_or_earlier_qmake
- /qt-5/qmake-manual.html|qmake]] in order to build Doomsday. ===== SDK requirements (1.15) ===== ==== Doomsday client, server, and libraries ==== **Windows** The... ==== Building with Qt Creator ===== - Open **doomsday.pro** in Qt Creator. This is the main project fil... c component. Note, however, that most require the Doomsday 2 libraries (libcore, libgui, libappfw, libshell)
- 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
- getting_started_1.15_or_earlier
- u to get started on software development with the Doomsday Engine. ====== Before you begin ====== It is important to understand, that Doomsday is an open source project. Doomsday is licensed under the [[http://www.gnu.org/licenses/gpl.html|GNU GPL v... in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty o
- 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
- automated_build_system
- releases for the project. ===== Overview ===== Doomsday's automated build system has been set up for dail... tem also generates an RSS feed with information about each build. Additionally, the stable branch is ch... 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 ==
- 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 c... d tool. After building, you must still deploy the binaries (e.g., using ''make install'') because Doomsday expects a particular runtime directory layout.
- 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
- repository|Subversion]], it's feasible to think about 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
- player_controls
- this works in the client/server architecture that Doomsday is using. ===== Motivation ===== Why are play... must be able to respond to PlayerThink's query about the velocity and offset affecting a particular lo... control of a specific player. These are composed out of multiple sources of data, i.e., all the device... uted. The control code should not need to know about the axis bindings. The bindings management update
- 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
- file_system
- e ''de::FS'' class is the main interface to the [[Doomsday 2]] internal file system. It maintains a tree of ... the tree. It also contains semantic information about the structure and content of the tree, allowing o... s are responsible for deciding when instances get out-of-date and need to be deleted (pruning). Pruning
- libdeng2_code_guidelines
- izes the coding conventions and practices used in Doomsday 2.0 (libdeng2 library). * more modular: core,... both function name and the error description (without a period in the end) -- see the existing throws i
- 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 ====== *