Recent Posts

81

Development / Re: It's year 2026, so I think some text like: 2024-2025 can be updated to 2026

« Last post by ollydbg on April 02, 2026, 12:32:04 pm »

I mean some text in our code base, such as "copy right 2004 - 2025 Code::Blocks team" like text should be updated to "2004 - 2026".

82

Development / Re: It's year 2026, so I think some text like: 2024-2025 can be updated to 2026

« Last post by cppuser on April 02, 2026, 11:57:40 am »

I don't understand the title to be honest. 
But I vote for git, even I am not  a developer for codeblocks yet, I will be one day I hope, I am reading the code to see how it is organized.
I have some ideas to try on codeblocks which I use daily  for my personal development on my projects.
I have used svn older time at work, but I prefer git.

83

Help / Re: wx3.3.x library build

« Last post by stahta01 on April 02, 2026, 07:58:57 am »

Look for wx33_64.cbp to use wxWidgets 3.3.

84

Help / Re: wx3.3.x library build

« Last post by stahta01 on April 02, 2026, 07:57:08 am »

I rebuilt wx3.3.2 after removing CFG=64 from my make command.
Then tried rebuilding codeblocks from source, but it continued failing because wxmsw32u couldn't be found. Vazd, from wxWidgets, says that that dll is made but hasn't been in any wxWidgets releases since probably before wx3.0. The question is: Is it coming from the v23828 nightly, that I was using as a host?

Doesn't cmake only make a makefile generally? You must of had another step or two to make the wx3.3 library?  Does your library contain dll files?

Why are you building the wx3.3 and thinking it will create an wx3.2 DLL?

Tim S.

85

Help / Re: wx3.3.x library build

« Last post by stahta01 on April 02, 2026, 07:53:58 am »

Look at the build log!
Then look at the name of the DLL and the path to the DLL.
See what is wrong.

Tim S.

86

Help / Re: wx3.3.x library build

« Last post by Frank_CB on April 02, 2026, 05:58:30 am »

I rebuilt wx3.3.2 after removing CFG=64 from my make command.
Then tried rebuilding codeblocks from source, but it continued failing because wxmsw32u couldn't be found. Vazd, from wxWidgets, says that that dll is made but hasn't been in any wxWidgets releases since probably before wx3.0. The question is: Is it coming from the v23828 nightly, that I was using as a host?

Doesn't cmake only make a makefile generally? You must of had another step or two to make the wx3.3 library?  Does your library contain dll files?

87

Help / Adding additional compiler

« Last post by JoeH on April 02, 2026, 05:06:03 am »

I have an old computer, running Windows XP, that I want to do some FORTRAN programming on.  I have installed CB17.12 and it works fine for C and C++.  The gfortran compiler is not available.  The only compiler .exe files that appear in the MinGW/bin directory are for C and C++.  I reinstalled CodeBlocks to be sure I selected the Fortran compiler for installation.  I had requested everything to be installed.  The options_gfortran.xml file does exist in the share/CodeBlocks/compilers directory.

Is there a way to add the gfortran compiler?

Thanks

Joe

88

Help / Re: wx3.3.x library build

« Last post by stahta01 on April 02, 2026, 04:55:01 am »

Try editing the "WX_CFG" under the project custom variables.
Any luck?

89

Help / Re: wx3.3.x library build

« Last post by stahta01 on April 01, 2026, 11:49:41 pm »

The "CFG=64" likely means you need to edit the cbp file to file the DLL

Edit: Try editing the "WX_CFG" under the project custom variables.

Unix like systems supports configure/make build method. I use MSys2 MinGW UCRT64 environment.

Tim S.

90

Help / Re: wx3.3.x library build

« Last post by Frank_CB on April 01, 2026, 10:10:02 pm »

I downgraded to winlib's gnu/gcc 15.1.0 compiler. Then, I used "mingw32-make.exe -f makefile.gcc CFG=64 BUILD=Release SHARED=1 MONOLITHIC=1" to  successfully build wx3.2.8.

What is the configure/make method you used for codeblocks? The usual method, that I use, is to execute a host codeblocks and then open the source wx32_64.cbp. Now, I'm getting failures because wxmsw32u cannot be found. Any ideas why it cannot find that dll file?