Code::Blocks Forums

User forums => Help => Topic started by: xblitz on December 12, 2023, 10:35:25 pm

Title: Problem to compile codeblocks
Post by: xblitz on December 12, 2023, 10:35:25 pm
Hello

I try to compile codeblocks from scratch. I folllowing thi guide:

https://wiki.codeblocks.org/index.php/Installing_Code::Blocks_from_source_on_Windows#Overview

I use this version of mingw (64bit of course): https://github.com/brechtsanders/winlibs_mingw/releases/download/13.2.0posix-17.0.5-11.0.1-ucrt-r3/winlibs-x86_64-posix-seh-gcc-13.2.0-mingw-w64ucrt-11.0.1-r3.7z

Code
||=== Build: tinyXML in Code::Blocks wx3.1.x (64 bit) (compiler: GNU GCC Compiler) ===|
||=== Build: AutoRevision in Code::Blocks wx3.1.x (64 bit) (compiler: GNU GCC Compiler) ===|
||=== Build: ConsoleRunner in Code::Blocks wx3.1.x (64 bit) (compiler: GNU GCC Compiler) ===|
||=== Build: Squirrel in Code::Blocks wx3.1.x (64 bit) (compiler: GNU GCC Compiler) ===|
||=== Build: scintilla in Code::Blocks wx3.1.x (64 bit) (compiler: GNU GCC Compiler) ===|
H:\wxWidgets-3.2.4\include\wx\platform.h|159|fatal error: wx/setup.h: No such file or directory|
||=== Build finished: 1 error(s), 0 warning(s) (0 minute(s), 1 second(s)) ===|

Can someone help me?  :)

Regards
Title: Re: Problem to compile codeblocks
Post by: stahta01 on December 12, 2023, 10:48:15 pm
You need to replace "31" with "32" in those directions.

Tim S.
Title: Re: Problem to compile codeblocks
Post by: xblitz on December 12, 2023, 10:54:01 pm
I suppose you mean "open CodeBlocks_wx32_64.cbp instead of CodeBlocks_wx31_64"....

I get same error :-/

Something wrong in wxwidgets compile process? it's identical to wx 3.1?
Title: Re: Problem to compile codeblocks
Post by: stahta01 on December 12, 2023, 10:55:12 pm
I suppose you mean "open CodeBlocks_wx32_64.cbp instead of CodeBlocks_wx31_64"....

I get same error :-/

Then, you likely failed to build wxWidgets; but, it might be another mistake. Without a build log no one can help you.
https://wiki.codeblocks.org/index.php/FAQ-Compiling_(errors)#Q:_How_do_I_troubleshoot_a_compiler_problem.3F (https://wiki.codeblocks.org/index.php/FAQ-Compiling_(errors)#Q:_How_do_I_troubleshoot_a_compiler_problem.3F)
Title: Re: Problem to compile codeblocks
Post by: xblitz on December 12, 2023, 10:57:15 pm
build log no one can help you.

wxwidgets standard output is a very long long file and useless... how can I perform a useful log
Title: Re: Problem to compile codeblocks
Post by: stahta01 on December 12, 2023, 11:21:37 pm

wxwidgets standard output is a very long long file and useless... how can I perform a useful log

I was talking about the CB build log building Code::Blocks
Title: Re: Problem to compile codeblocks
Post by: xblitz on December 12, 2023, 11:33:30 pm
I found the mistake: the C::B guide says:

Code
To compile wxWidgets in 64-bit mode add CFG=64 to the build line that is given next or use a compiler that defaults to 64 bit output. For example, MinGW-w64 has toolchains targetting 32 bits and others targetting 64 bits.

So, I pass the argument CFG=64 in command line... now I try to recompile WwWidgets without this option and it seems work properly: codeblocks release is still compiling without any error, for now.

EDIT:

||=== Build finished: 0 error(s), 4 warning(s) (7 minute(s), 40 second(s)) ===|
Title: Re: Problem to compile codeblocks
Post by: stahta01 on December 12, 2023, 11:36:22 pm
I found the mistake: the C::B guide says:

Code
To compile wxWidgets in 64-bit mode add CFG=64 to the build line that is given next or use a compiler that defaults to 64 bit output. For example, MinGW-w64 has toolchains targetting 32 bits and others targetting 64 bits.

So, I pass the argument CFG=64 in command line... now I try to recompile WwWidgets without this option and it seems work properly: codeblocks release is still compiling without any error, for now.

EDIT:

||=== Build finished: 0 error(s), 4 warning(s) (7 minute(s), 40 second(s)) ===|

Thanks for that feedback. I hope someone re-writes the directions; but, it is a small hope. I just do not have the energy to do it myself.

Tim S.