Welcome to the ZDoom Forums!

Actually, /proc/cpuinfo is a pseudo-file provided by the kernel, itself. And yes it is quite well expected that on Linux you use /proc information - virtually all Linux tools that matter do so, anyhow. Your expection is quite wrong; the format of /proc/cpuinfo varies wildly between processor ...

On Windows I can detect the number of physical cores and report that. On Linux and macOS I am stuck because they do not have an API for that piece of info I can easily use. Surely this should be easy (using popen(3) on Linux). $ lscpu --parse=cpu,node,socket,core,maxmhz # The following is the ...

gzdoom/src/d_anonstats.cpp:14:10: fatal error: i_mainwindow.h: No such file or directory 14 | #include "i_mainwindow.h" | ^~~~~~~~~~~~~~~~ compilation terminated. make[2]: *** [src/CMakeFiles/zdoom.dir/build.make:1441: src/CMakeFiles/zdoom.dir/d_anonstats.cpp.o] Error 1 make[2]: *** Waiting for ...

Data point: Using an -m32 build on a x64 CPU, GZDoom 4.8.1 - - SDL version ... CPU Vendor ID: GenuineIntel Name: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz Family 6, Model 140, Stepping 1 Features: SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 AVX AVX2 AVX512 F16C FMA3 BMI1 BMI2 HyperThreading Using video ...

So I fell prey to autogenerated source archives which have little benefit over `git clone` I figure. Normally, when source tarballs are made, a certain standard is customary; such includes, for example, running autoreconf (where applicable), pulling submodules for completeness, and/or making GPG ...

Anyone seen this before? gzdoom-g4.5.0> mkdir build; cd build; cmake ..; make [...] [ 1222s] /usr/bin/make -f wadsrc_widescreen/CMakeFiles/game_widescreen_gfx_pk3.dir/build.make wadsrc_widescreen/CMakeFiles/game _widescreen_gfx_pk3.dir/build [ 1222s] make[2]: Entering directory '/home/abuild ...

Redneckerz wrote:It reads like a processor name though (LZDoom 386)

The pareidolia of modern times…

On the upside, I can actually input Japanese characters into gzdoom quite successfully, with only little bugs remaining. (1. only the first Unicode character of the multi-character IME output is copied over. 2. Player Setup submenu does not use the new font yet.) Of course, the usefulness of such ...

Due to CMakeLists.txt only enabling vulkan for x86_64, it fails to build on all other architectures: if( ${ZDOOM_TARGET_ARCH} MATCHES "x86_64" ) set( HAVE_VM_JIT ON ) set( HAVE_VULKAN ON ) endif() [ 233s] /home/abuild/rpmbuild/BUILD/gzdoom-4.0.0/src/posix/sdl/sdlglvideo.cpp: In destructor 'virtual ...

https://www.moddb.com/mods/wolfendoom-blade-of-agony/downloads/blade-of-agony-chapter-2-v20-standalone Extract just boa_c2.pk3 (not brightmaps.pk3, lights.pk3 and gzdoom.pk3), then load that. ("gzdoom -iwad /usr/share/doom/doom2.wad -file boa_c2.pk3" for me). gzdoom 3.7.1 rejects some actor info ...

Some distributions are on libfluidsynth.so.2 already. Which distributions? That would be openSUSE. Now that you mentioned it, I looked at Gentoo and Arch, and am surprised to not find 2.x there yet, because I remember that community to be generally quick. 2.x came out a month ago, Sep 14 2018. On ...

I am being told by proxy that fluidsynth output, in a default build, is broken. Just grepping reveals: 13:56 a4:../gzdoom/gzdoom > git grep fluidsynth.so. src/sound/mididevices/music_fluidsynth_mididevice.cpp:#define FLUIDSYNTHLIB1 "libfluidsynth.so.1" Some distributions are on libfluidsynth.so.2 ...

ILP32 can be faster in some cases, depending on the CPU type, amount of memory shuffled around, etc. http://www.osnews.com/story/5768/Are_64-bit_Binaries_Really_Slower_than_32-bit_Binaries_/page1/ (very old page) For a x86_64 CPU type though, one should be exploiting all registers and choose an ...

So just that I get this straight... is this just two separate builds of the same source, or really two independent, diverging source releases? In the latter case, the git repo is missing a 3.5.0-legacy or so tag. $ glxinfo [...] Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 ...

Import Timidity++ into GZDoom directly This somehow broke timidity playback under Linux. In 3.2.5, a separate process would be spawn and play the music, in 3.3.0 no such thing happens and it falls back to fluid. Console says: GZDoom 3.3.0 - - SDL version Compiled on M_LoadDefaults: Load system ...