Trouble compiling Chocolate Doom (Code::Blocks)

[Adam Oker]

Hi, so after i compiled Chocolate Doom with MSYS2 (which took an insane amount of time to compile ;-;), i found a different page, one for compiling with Code::Blocks, so i decided to try it out since i'm more familiar with Code::Blocks and so hopefully compilation won't take as long.

So, i started trying to compile, i followed the steps up until reached the actual compiling step, where it then threw me this error.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

There are some other errors, but i'll tackle them one after the other. I also left the build options basically untouched.

For now i need help trying to fix this error.

I used : 

-Chocolate Doom release 2.30.2's source (the latest version didnt have a codeblocks folder)

-SDL2 2.30.2

-SDL2_mixer 2.8,0

-SDL2_net 2.2.0

 

Thanks in advance!

Edited April 9, 2024 by Adam Oker
typo

[Shepardus]

Version 2.30.2 predates the migration from SDL1 to SDL2 (Chocolate Doom 3.0.0 is when that happened).

 

The Code::Blocks project was removed from the repo in 2018 in favor of the CMake and Autotools build systems. You're probably better off looking up how to integrate a CMake or Autotools project with Code::Blocks. Or just write your code in Code::Blocks and run your builds from the MSYS terminal.

[Adam Oker]

2 hours ago, Shepardus said:

Version 2.30.2 predates the migration from SDL1 to SDL2 (Chocolate Doom 3.0.0 is when that happened).

 

The Code::Blocks project was removed from the repo in 2018 in favor of the CMake and Autotools build systems. You're probably better off looking up how to integrate a CMake or Autotools project with Code::Blocks. Or just write your code in Code::Blocks and run your builds from the MSYS terminal.

I see, i guess i'll just use CMake...

Edited April 9, 2024 by Adam Oker

[Adam Oker]

2 hours ago, Shepardus said:

Version 2.30.2 predates the migration from SDL1 to SDL2 (Chocolate Doom 3.0.0 is when that happened).

 

The Code::Blocks project was removed from the repo in 2018 in favor of the CMake and Autotools build systems. You're probably better off looking up how to integrate a CMake or Autotools project with Code::Blocks. Or just write your code in Code::Blocks and run your builds from the MSYS terminal.

So, i tried using CMake, it went smoothly until i finished configuring, then it just throws me this error :

 

I don't even know where cc1.exe is, not cc11plus.exe. And if i avoid these errors CMake just tells me that configuration is incomplete

So, where is cc1.exe even located, i used msys2 mingw32's C/C++/Fortran compilers btw.

Help

[Shepardus]

On cc1/cc1plus: https://unix.stackexchange.com/a/77781

 

Frankly I would recommend building from the terminal, which you've already done. All the (admittedly little) source port work I've done has been with Vim and a terminal window, and I've found it to be plenty good enough for my purposes. Don't get bogged down with tooling before you know you need it.

[Adam Oker]

1 minute ago, Shepardus said:

On cc1/cc1plus: https://unix.stackexchange.com/a/77781

 

Frankly I would recommend building from the terminal, which you've already done. All the (admittedly little) source port work I've done has been with Vim and a terminal window, and I've found it to be plenty good enough for my purposes. Don't get bogged down with tooling before you know you need it.

 

If you're referring to MSYS2, it was extremely slow, and it would suck if i had to wait for chocolate doom to compile for another 2 hours for the most smallest of changes.

I mean, if you have any tips on speeding it up, i'm up

[Shepardus]

Two hours is incredibly slow; my 12 year old laptop does a clean build (starting from the autogen script) in about one or two minutes. Your computer is either far lower-spec than mine or there's something else hogging its resources. If it's slow in the terminal, it's not going to be any faster through Code::Blocks, since you'd be doing the same thing but in a GUI.

 

If you have a multi-core processor you can generally speed things up by using the -j flag with make, followed by a number, to have it run multiple jobs in parallel, for example "make -j4" on a quad-core computer.

 

Incremental builds should also be much faster; after the first build, running make again will only rebuild the parts that have changed (assuming you didn't run "make clean" which removes all the previously built stuff), so if you've only changed a few files then rebuilding should just take a couple seconds.