51
Help / Re: The tabs close when you save a file.
« Last post by christo on August 11, 2026, 05:17:13 am »Is it possible to share your .cbp file also?
News:
Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!
Recent Posts
52
Help / Re: The tabs close when you save a file.
« Last post by dthu on August 11, 2026, 04:36:58 am »After deleting the file, the problem persists. An identical file was generated.
53
Help / Re: The tabs close when you save a file.
« Last post by Miguel Gimenez on August 10, 2026, 11:05:37 am »Delete the .layout file, it will be recreated.
54
Help / The tabs close when you save a file.
« Last post by dthu on August 09, 2026, 08:34:46 pm »I had a project started with the source code located in its default position. I decided to move the code. In C::B, I removed all the files and then added them to their new location. I don't know if it's related, but since then, the program closes the tabs associated with the project files every time I save or compile. I realized that the .layout file is different from other projects, so I'm placing it here.
I've experienced this problem in both the stable version and r13923 on Linux.
I've experienced this problem in both the stable version and r13923 on Linux.
Code
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<CodeBlocks_layout_file>
<FileVersion major="1" minor="0" />
<ActiveTarget name="Debug" />
</CodeBlocks_layout_file>
55
General (but related to Code::Blocks) / Re: "iCCP: known incorrect sRGB profile" when using wxWidgets-3.2.11
« Last post by Miguel Gimenez on August 09, 2026, 12:52:38 pm »I will fix the png next week, currently I do not have access to the repository.
56
Help / Re: Code::Blocks always add #ifndef HEADER_ on some .h files
« Last post by MortenMacFly on August 08, 2026, 06:34:11 pm »It seems you have installed / activated a plugin called "Header Guard" (headerguard.dll).
De-activate or un-install this plugin if you don't need it and this will be gone.
De-activate or un-install this plugin if you don't need it and this will be gone.
57
General (but related to Code::Blocks) / Re: Is there any expectation or desire to compile Code::Blocks with clang/clang++
« Last post by blauzahn on August 06, 2026, 08:31:52 pm »Even without actually compiling cb with llvm/clang you can benefit A LOT from its toolbox to find errors and dubious code.
1) Use the clangd_client cb-plugin. I only activate it temporarily, look at its findings and deactivate it afterwards due to its early stage.
2) Use clang-tidy as a "compiler" on any c++ project from within cb. Like with compiler warnings, clicking onto one jumps to the corresponding code line. This one I use very often. I started using it with cb over 10 years ago.
3) Use scan-build from the commandline when building cb or any other project that compiles makefiles (e.g. via cmake). Gives a nice report.
Apart from llvm/clang I still recommend the cb-plugin for cppcheck.
The tools do have false positives. You can configure .clang-tidy. I disabled some warnings but in general I like to keep warnings on. At spots with false positives you can apply local suppressions (NOLINT, NOLINTNEXTLINE, cppcheck-suppress etc.). When using one of the tools for the first time on a larger codebase you might be flooded with warnings. Don't dispair. One strategy to attack the list systematically is to disable all but one type of warning. Fix those and proceed with the next type of warning. This might also happen after an update of one of the tools. A week ago, llvm forked clang-23 and started to provide packages for clang-24. The latter added a new check for [misc-const-correctness]. I like it.
1) Use the clangd_client cb-plugin. I only activate it temporarily, look at its findings and deactivate it afterwards due to its early stage.
2) Use clang-tidy as a "compiler" on any c++ project from within cb. Like with compiler warnings, clicking onto one jumps to the corresponding code line. This one I use very often. I started using it with cb over 10 years ago.
3) Use scan-build from the commandline when building cb or any other project that compiles makefiles (e.g. via cmake). Gives a nice report.
Apart from llvm/clang I still recommend the cb-plugin for cppcheck.
The tools do have false positives. You can configure .clang-tidy. I disabled some warnings but in general I like to keep warnings on. At spots with false positives you can apply local suppressions (NOLINT, NOLINTNEXTLINE, cppcheck-suppress etc.). When using one of the tools for the first time on a larger codebase you might be flooded with warnings. Don't dispair. One strategy to attack the list systematically is to disable all but one type of warning. Fix those and proceed with the next type of warning. This might also happen after an update of one of the tools. A week ago, llvm forked clang-23 and started to provide packages for clang-24. The latter added a new check for [misc-const-correctness]. I like it.
58
General (but related to Code::Blocks) / Re: Is there any expectation or desire to compile Code::Blocks with clang/clang++
« Last post by christo on August 06, 2026, 05:51:32 pm »Looks like Morten is working on building C::B for clang/arm. Recent svn changs shows many fixes the warnings.
59
General (but related to Code::Blocks) / Re: "iCCP: known incorrect sRGB profile" when using wxWidgets-3.2.11
« Last post by ollydbg on August 06, 2026, 09:44:11 am »I also see this kind of message in my console windows in my own built application, which is built against the wx library from msys2/mingw64 platform. I see the wx version is:
https://packages.msys2.org/base/mingw-w64-wxwidgets3.2
https://packages.msys2.org/base/mingw-w64-wxwidgets3.2
60
General (but related to Code::Blocks) / Is there any expectation or desire to compile Code::Blocks with clang/clang++
« Last post by everSome on August 06, 2026, 05:31:02 am »It might be useful to compile Code::Blocks with the clang compiler as the warnings and once in a while the errors exposed are somewhat different. What think ye?