Recent Posts

91

Help / Re: How to fix the translation error of zh_CN

« Last post by gd_on on November 27, 2025, 02:11:11 pm »

Effectively, in zh_CN.mo as distributed on C::b web site (at least in the nosetup.zip version), there is this error (but I can't correct that). Probably, this zh_CN had a problem or was not updated as it should. The last version on launchpad, .po and .mo are OK and more, has been regularly updated (last contribution by Grit Clef: 2025-10-01)

92

Help / Re: How to fix the translation error of zh_CN

« Last post by Cubestone.Wang on November 27, 2025, 12:48:06 pm »

First, thank you for answer. I just finished to change it for myself.

And then, I see the new website and download it, the content translation is right ( translated on 2019-06-21, reviewed on 2024-03-27)



So, the question: I download software package (version 25.03) from "https://www.codeblocks.org/downloads/binaries/#imagesoswindows48pnglogo-microsoft-windows". And the zh_CN file just is built-in (2025-03-31). When you use "msgunfmt zh_CN.mo -o zh_CN.po" to check it, just see "!" in content (just like what I said). Anyone who interested in it could do these step for check.




Thus, what's happened? May in CI/CD process, it is not get ".po" file from the new translate website?

93

Help / Re: How to fix the translation error of zh_CN

« Last post by gd_on on November 27, 2025, 11:58:28 am »

More, from this page you can also download the .po file (source) and/or the .mo file. If you have still problems, you can try to use poedit on the .po file to correct it and produce your own .mo file. You can also correct some bad or not correct translations on launchpad and submit them (you just need to have already a launchpad account or create one).

94

Help / Re: How to fix the translation error of zh_CN

« Last post by Miguel Gimenez on November 27, 2025, 11:44:37 am »

The launchpad page you saw is obsolete, please use this

95

Help / How to fix the translation error of zh_CN

« Last post by Cubestone.Wang on November 27, 2025, 10:05:20 am »

When I use 25.03 version in zh_CN, there is a "!" before the content, see the following image:

After using "msgunfmt zh_CN.mo -o zh_CN.po", I confirm it:

And then, I search something, but in source code, no zh_CN file, in Nightly builds, no zh_CN file, in translate website, the current content is translated just in 2006-07-17:




So where is the question, in building process?
I post the message in this forums, and wait someone could fix it. Or maybe post it in "https://sourceforge.net/p/codeblocks/tickets/"?

96

General (but related to Code::Blocks) / OpenWatcom (W32) Compiler template problem

« Last post by Tim on November 25, 2025, 05:41:59 pm »

System = Windows XP SP3

Codeblocks 8.02 and 20.03 (Possibly others in between)

I've just noticed a problem with the "Open Watcom" compiler template/Plugin.

If a "copy" is made of the "OpenWatcom (W32) Compiler" template, Say for example,  "Copy of OpenWatcom (W32) Compiler" (Without any modifications)

Then an attempt to compiler & link a basic "Console" application with it, it will generate a very different warning & error output from the original template.

97

Using Code::Blocks / Re: Code::Blocks and Intel OneAPI?

« Last post by ThierryD on November 23, 2025, 05:34:43 pm »

Hi,

My first experience with OneAPI Intel Compiler was with version 2024.2 [and VS2022] because tle lastest version of this compiler is now based on LLVM architecture.
First consequence, this compiler need to lean with "full" environment devlopment like MinGW or Visual Studio.
Root binary directory of OneAPI is : C:\Program Files (x86)\Intel\oneAPI\compiler\latest\bin ("latest" is a link on real directory "2024.2"), it's very useful to simplify configuration.
Note that exist also a directory " C:\Program Files (x86)\Intel\oneAPI\compiler\latest\bin32" to store libraries and DLL of this compiler "compatible" with 32 bit architecture, but
binary directory of OneAPI compiler is always ...\bin. To choose 32 or 64 bit generation, you must use option "-m32|-m64" during compilation and "/MACHINE:X86|X64" during linkage if needed.

NB : Version 2024.2 is last version to support 32 bit generation. Intel has abandoned this feature with newer version like 2025.nn .
NB2 : To developer of CB, reference of One API Intel Compiler is "very" obsolete ... executable of C compiler is now "icx" and this of C++ compiler is "icpx".
       Note that in configuration into CB, it's mandatory to distinguish C compiler to C++ compiler by name.of OneAPI

Yesterday, I changed configuration of Visual Studio to update to VS 2026 "Community" last available for free use ... and I tested into CB with no difficulty ...
Just to precise, I use environment variable into configuration in CB to translate version number of VS version and VS number in name of directories used.
Good precaution, because I just change value of env variable "VS_version" from "2022" to "18" (and yes, not "2026" !!...) and "VS_num" from "14.44.35207" to "14.50.35717" .
Nothing else to change, VS 2026 wrk perfectly with CB.

And, because I'm curious about newer version of "interesting" compilers, I try to change to newer version of One API Intel Compiler : 2025.3.
It's just impossible "at date" because installer tool of OneAPI control presence of VS 2019 or VS2022 ... but not also VS 2026.

Then, I tested if my "precedent" version of OneAPI Intel Compiler with version 2024.2 configured successfully with VS 2022 continue to work with VS 2026.
And the response is "Yes". Only installation tool of OneAPI claim prerequisite VS 2019 or VS2022, use One API Intel Compiler version 2024.2 leaned with VS 2026 work perfectly in CB (or outside IDE). Good new !

Good luck to experiment OneAPI compiler into CB.

Thierry.

 

98

Nightly builds / Re: The 25 October 2025 build (13754) is out.

« Last post by Михаил Агарков on November 21, 2025, 05:43:26 pm »

Code::Blocks launches extremely slowly on Windows 11, including both the official version and the nightly build version. My computer runs on an x64 system.

Windows 11 in general is slow, since MS decided that the taskbar and start menu should be made in React Native, that's one of the many terrible performance decisions they made which is why I'm staying on Windows 10.

99

Nightly builds / Re: The 25 October 2025 build (13754) is out.

« Last post by 1978544461@qq.com on November 21, 2025, 02:58:50 pm »

Code::Blocks launches extremely slowly on Windows 11, including both the official version and the nightly build version. My computer runs on an x64 system.

100

Using Code::Blocks / Re: Test CB with WSL Ubuntu 24.04

« Last post by Miguel Gimenez on November 20, 2025, 07:15:20 pm »

At least on MSW they are disabled until you open a project. When you open a project all are enabled, even if the executable paths are not configured (use "Open preferences" to configure them if they are not in the path).