Is this instruction
https://zdoom.org/wiki/Compile_ZDoom_on_Windows
still actual for compiling gzdom?
Because it speaks of zdoom, not gzdoom, and visual c++ from 2015 years, and link to downloads it lead to visual c++ from 2017 years.
Compiling gzdoom for dummies
- Graf Zahl
- Lead GZDoom+Raze Developer
- Posts: 49067
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: Compiling gzdoom for dummies
GZDoom compiles with Visual C++ 2015 and 2017. But you'll have problems finding the 2015 version these days because it has long been replaced with 2017 by Microsoft.
Re: Compiling gzdoom for dummies
Ummm.....what component I need to install?
Because I get lost what to choose in between net framework ASP .NET, VSTO, office for visual studio, VC ++ 2017 15.7 v14.14, etc.
Because I get lost what to choose in between net framework ASP .NET, VSTO, office for visual studio, VC ++ 2017 15.7 v14.14, etc.
Re: Compiling gzdoom for dummies
Desktop development with C++ should be enough.
Re: Compiling gzdoom for dummies
I assume that to run debug in visual studio I must download fmodex.dll by myself!?
Because without it visual studio throw error " Unable to start 'path to all_build' Cant find file" while simple start of gzdoom as program run it with "sound init failed. using nosound" lines in startup window with midi only music.
Or there are way to bypass this?
Because without it visual studio throw error " Unable to start 'path to all_build' Cant find file" while simple start of gzdoom as program run it with "sound init failed. using nosound" lines in startup window with midi only music.
Or there are way to bypass this?
Re: Compiling gzdoom for dummies
To debug with ALL_BUILD set as startup project you need to specify path to executable manually in project properties.
FMOD Ex was dropped since 3.0 but you should copy all .dll files from the latest release to a folder with built executable.
FMOD Ex was dropped since 3.0 but you should copy all .dll files from the latest release to a folder with built executable.
Re: Compiling gzdoom for dummies
Then looks like I do somthing wrong.
Because after I manage to turn on debug mode, in VS console start to shows up errors like "C:\Windows\kernel.dll, cant find or open PDB file."
But anyway, it works with some changes that I add to it, so I think this is not so important.
Because after I manage to turn on debug mode, in VS console start to shows up errors like "C:\Windows\kernel.dll, cant find or open PDB file."
But anyway, it works with some changes that I add to it, so I think this is not so important.
- Graf Zahl
- Lead GZDoom+Raze Developer
- Posts: 49067
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: Compiling gzdoom for dummies
These errors are meaningless. They only tell you that you do not have debug symbols for the system DLLs.