1
Help / Re: dont parse std::filesystem
« Last post by Miguel Gimenez on Yesterday at 10:08:09 am »Disable the CodeCompletion plugin and install the new Clangd_client plugin, see this.
News:
The new Release 25.03 is out! You can download binaries for Windows and many major Linux distros here .
Recent Posts
2
General (but related to Code::Blocks) / Re: Problem with Code::Block IDE
« Last post by Miguel Gimenez on Yesterday at 10:06:44 am »Did you install C::B using Flatpak? It is known to block some non-standard folders.
3
General (but related to Code::Blocks) / Problem with Code::Block IDE
« Last post by membercatch on Yesterday at 05:20:06 am »I need some assistance with Zorin 16 Core and Code::Blocks IDE in a VMware virtual machine.
I've started working on a program, and it requires a header file called X11/Xmu/WinUtil.h. It is found in the /usr/include/X11/Xmu/ folder after installing the libxmu-dev package, but Code::Blocks appears to be unable to recognize the /usr/include/X11 folder when I attempt to add it to the project's list of includes.
However, it does recognize some of the other folders in the /usr/include directory, but not this one.
So I'm curious what the difference is and the steps required to get Code::Blocks for seeing the X11 folder. What do I need and do to make this work? What is missing?
I've started working on a program, and it requires a header file called X11/Xmu/WinUtil.h. It is found in the /usr/include/X11/Xmu/ folder after installing the libxmu-dev package, but Code::Blocks appears to be unable to recognize the /usr/include/X11 folder when I attempt to add it to the project's list of includes.
However, it does recognize some of the other folders in the /usr/include directory, but not this one.
So I'm curious what the difference is and the steps required to get Code::Blocks for seeing the X11 folder. What do I need and do to make this work? What is missing?
4
Help / Re: dont parse std::filesystem
« Last post by stahta01 on July 01, 2025, 02:32:05 pm »I do not use the old or new CC code completion.
Link to FAQ; to help you it is normally required to post the Code::Blocks version and Operating System (OS) info.
Edit: MinGW does say Windows; the version likely does not matter; but, whether 64 bit OS does sometime matter when using debugger.
https://wiki.codeblocks.org/index.php/FAQ-Settings#Q:_How_do_I_get_Code_Completion_to_work.3F
Tim S.
Link to FAQ; to help you it is normally required to post the Code::Blocks version and Operating System (OS) info.
Edit: MinGW does say Windows; the version likely does not matter; but, whether 64 bit OS does sometime matter when using debugger.
https://wiki.codeblocks.org/index.php/FAQ-Settings#Q:_How_do_I_get_Code_Completion_to_work.3F
Tim S.
5
Help / dont parse std::filesystem
« Last post by viewrock on July 01, 2025, 01:30:36 am »Hello, i try to learn std::filesystem
do this:
compile flag to c++20 iso standart
#include <filesystem>
and when a try std::filesystem:: - i have only ::__file_clock in code complection
but all the tutorial examples compile successfully!!!.
I dont understand how to fix code complection to <filesystem>
i use codeblocks with minGW.
ps:: on visual studio all works correctly.
ps2:: std::string is broken too.)
ps3:: Sorry for my English.
do this:
compile flag to c++20 iso standart
#include <filesystem>
and when a try std::filesystem:: - i have only ::__file_clock in code complection
but all the tutorial examples compile successfully!!!.
I dont understand how to fix code complection to <filesystem>
i use codeblocks with minGW.
ps:: on visual studio all works correctly.
ps2:: std::string is broken too.)
ps3:: Sorry for my English.
6
Help / Re: Code blocks does not work with Mac Sequoia
« Last post by Miguel Gimenez on June 30, 2025, 12:42:36 pm »Future spam added to radar.
7
Help / Re: Code blocks does not work with Mac Sequoia
« Last post by peake01 on June 30, 2025, 11:39:16 am »Safe Mode in Code::Blocks disables some plugins to help troubleshoot issues. When this mode is enabled, plugins needed for debugging, such as GDB, may be disabled, making debugging on the Mac impossible and making it difficult to diagnose errors.
8
General (but related to Code::Blocks) / Re: Debug "arrow" too hard to see
« Last post by JimC on June 29, 2025, 07:38:05 pm »Not quite what I wanted, but definitely an improvement. Thanks!Not quite what I wanted, but definitely an improvement. Thanks!
9
General (but related to Code::Blocks) / Re: Debug "arrow" too hard to see
« Last post by Pecan on June 29, 2025, 07:23:00 pm »When debugging, I find the arrow showing the current line really hard to spot. I've had a poke around the editor settings but can't see anything relevant... is there a way to change the arrow's colour or size?
You can highlight the current debugger line with Setting/Editor/Other Editor Settings(tab)/Highlight line under caret.
10
General (but related to Code::Blocks) / Debug "arrow" too hard to see
« Last post by JimC on June 29, 2025, 06:01:47 pm »When debugging, I find the arrow showing the current line really hard to spot. I've had a poke around the editor settings but can't see anything relevant... is there a way to change the arrow's colour or size?