ZDoom

And that said, take a guess where the CQ fonts were taken from... ;) Sorry, I think I misunderstood earlier. Are all the Chex Quest assets in the GZDoom pk3 coming from Charles Jacobi's Chex Quest 3? If so, then perhaps Jacobi is the current copyright owner for these assets. When I first contacted ...

I investigated a bit further to try to find the license for these assets. Heretic and Hexen I was able to track down the EULA for the Heretic and Hexen game assets: https://www.doomworld.com/eternity/activision_eula.txt SOFTWARE LICENSE AGREEMENT IMPORTANT - READ CAREFULLY: USE OF THIS PROGRAM IS ...

This license agreement should cover the assets derived from the Doom games, but are there any assets in the GZDoom pk3s derived from other games?

See Section 2: Permitted New Creations of the LICENSE.DOC file that accompanied the original releases of the game. 2. Permitted New Creations. Subject to the terms and provisions of this Agreement and so long as you fully comply at all times with this Agreement, ID grants to you the non-exclusive a ...

Demos are under an extremely restrictive license. You are not allowed, under any circumstances, to modify content in the shareware version, or to create content compatible with the shareware versions. There's very few things that are exclusive to the shareware versions anyway - I think the title ...

The brightmaps are a bit problematic because they are based on the original game content. so for all intents and purposes, consider both brightmaps.pk3 and zd_extra.pk3 as non-free because they contain copyrighted material that is needed to run the original games. Thank you for the quick reply. So ...

I am aware that an effort was made to separate non-free assets to their own pk3s (cf. https://forum.zdoom.org/viewtopic.php?f=4&t=57776), but I'm having trouble finding the specific license for these assets. Are the gzdoom.pk3 and lights.pk3 files licensed under specifically the GPL? What are the ...

Here's the Gentoo team's rationale for preferring external libraries by default: https://wiki.gentoo.org/wiki/Why_not_bu ... pendencies

You're right, it looks like the Timidity++ ZDoom wiki page lists the version this started as GZDoom version 3.3.0.

Ah, so in the past Timidity was linked externally; but now that the license allows it, Timidity will always be linked statically since it's provided internally with the GZDoom source code?

I am following the ZDoom wiki instructions to compile GZDoom for Linux . The timidity and wildmidi libraries are listed as optional build and runtime dependencies. Similarly, the dependencies installation examples for most of the Linux distros lists these packages in their install list. However ...

Thinking a bit further about this - we have to force the linking. The API of the GLSL compiler is not stable - I had to make a few minor code adjustments when I upgraded the compiler. @Graf: totally agree with you on the sacrilege thing. It seems some people still think it is the 80's or early 90's ...

I tracked down the cause of the issue. I'm running Gentoo Linux, and building GZDoom via a Gentoo ebuild. Gentoo passes several default configurations to CMake , and within these defaults I found the following: SET (BUILD_SHARED_LIBS ON CACHE BOOLEAN "") This was causing CMake to default to dynamic ...

I noticed the current gzdoom src/CMakeLists.txt file is unconditionally adding the "glslang", "SPIRV", and "OGLCompiler" libraries without first checking if they are installed on the system These libraries should be detected first before they are added to the link list. Source code of these ...

I am attempting to run GZDoom version 4.1.1 on a Linux x86_64 target. The following error is reported when the gzdoom executable is run: $ gzdoom gzdoom: error while loading shared libraries: libSPIRV.so: cannot open shared object file: No such file or directory It does not surprise me that libSPIRV ...