Recent Posts

1

General (but related to Code::Blocks) / Compilation error using wxWidgets 3.3.3

« Last post by everSome on Today at 04:27:58 am »

Is wxWidgets being too restrictive? I had no problems with r13882 & 3.3.2,
but with r13553 & 3.3.3 I get:

Code

g++.exe -Wall -m64 -std=gnu++20 -O3 -pipe -mthreads -fmessage-length=0 -fexceptions -DHAVE_W32API_H -D__WXMSW__ -D_WIN64 -DWXMAKINGDLL -DwxUSE_UNICODE -DWXMAKINGDLL_CHART -Wno-unused-local-typedefs -Wno-deprecated-declarations -march=haswell -fno-omit-frame-pointer -IC:\msys64\home\NateJoe\wxWidgets\wxRegEx_changes\NewConfig\wxWidgets-3.3.3\include -IC:\msys64\home\NateJoe\wxWidgets\wxRegEx_changes\NewConfig\wxWidgets-3.3.3\lib\gcc_dll\mswu -Iwxchart\include -c C:\msys64\home\NateJoe\CodeBlocks\codeblocks-code-r13883-trunk_Just333\src\plugins\contrib\wxContribItems\wxchart\src\pie3dchartpoints.cpp -o ..\..\..\.objs33_64\plugins\contrib\wxContribItems\wxChartCtrl\wxchart\src\pie3dchartpoints.o
In file included from C:\msys64\home\NateJoe\wxWidgets\wxRegEx_changes\NewConfig\wxWidgets-3.3.3\include/wx/window.h:2082,
from C:\msys64\home\NateJoe\wxWidgets\wxRegEx_changes\NewConfig\wxWidgets-3.3.3\include/wx/wx.h:36,
from C:\msys64\home\NateJoe\CodeBlocks\codeblocks-code-r13883-trunk_Just333\src\plugins\contrib\wxContribItems\wxchart\src\chartctrl.cpp:28:
C:\msys64\home\NateJoe\wxWidgets\wxRegEx_changes\NewConfig\wxWidgets-3.3.3\include/wx/msw/window.h:74:22: warning: 'virtual wxString wxWindow::GetLabel() const' was hidden [-Woverloaded-virtual=]
74 | virtual wxString GetLabel() const override;
| ^~~~~~~~
In file included from wxchart\include/wx/chartctrl.h:26,
from C:\msys64\home\NateJoe\CodeBlocks\codeblocks-code-r13883-trunk_Just333\src\plugins\contrib\wxContribItems\wxchart\src\chartctrl.cpp:32:
wxchart\include/wx/legendwindow.h:54:18: note: by 'wxString wxLegendWindow::GetLabel(int) const'
54 | wxString GetLabel(int n) const;
| ^~~~~~~~
C:\msys64\home\NateJoe\CodeBlocks\codeblocks-code-r13883-trunk_Just333\src\plugins\contrib\wxContribItems\wxchart\src\chartctrl.cpp: In member function 'void wxChartCtrl::OnScroll(wxScrollWinEvent&)':
C:\msys64\home\NateJoe\CodeBlocks\codeblocks-code-r13883-trunk_Just333\src\plugins\contrib\wxContribItems\wxchart\src\chartctrl.cpp:847:41: error: 'void wxScrollHelperBase::HandleOnScroll(wxScrollWinEvent&)' is private within this context
847 | wxScrolledWindow::HandleOnScroll( event );
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~
In file included from C:\msys64\home\NateJoe\wxWidgets\wxRegEx_changes\NewConfig\wxWidgets-3.3.3\include/wx/wx.h:83:
C:\msys64\home\NateJoe\wxWidgets\wxRegEx_changes\NewConfig\wxWidgets-3.3.3\include/wx/scrolwin.h:413:10: note: declared private here
413 | void HandleOnScroll(wxScrollWinEvent& event);
| ^~~~~~~~~~~~~~
Process terminated with status 1 (1 minute(s), 21 second(s))

2

Development / Re: Code::Blocks development for macOS

« Last post by Pecan on Yesterday at 11:17:06 pm »

Users usually become developers by tackling some of the tickets or submitting patches that interest them and will be of use to you and to the other users.

At least that's how I did it.

3

Development / Code::Blocks development for macOS

« Last post by debarshikundu0 on Yesterday at 10:00:51 am »

Hello all,
I have managed to compile and run the source code for Code::Blocks 25.03 on macOS Tahoe (M1 Mac mini with 16GB of Unified Memory)...
I understand that there are more Mac developers needed within the Code::Blocks project. The application is a bit buggy/laggy on macOS, to say the least.
I would like to become an official macOS developer for Code::Blocks. How can I go about achieving this goal?

Yours truly,

Debarshi Kundu

4

Plugins development / Re: cppcheck/vera wrong links

« Last post by Miguel Gimenez on July 01, 2026, 07:21:13 pm »

I have commited already, filling the Url with the Label value (dialog design forces using Label = Url to keep coherency).

Regarding the translation, here is not needed or desired, but wxSmith generates the _() automatically. In other cases translation of the Url may be helpful, for example if you want to use "google.com" in english and "google.fr" in french, or "microsoft.com" and "microsoft.com/fr".

5

Plugins development / Re: cppcheck/vera wrong links

« Last post by gd_on on July 01, 2026, 07:12:25 pm »

Here is a possible patch.

6

Plugins development / Re: cppcheck/vera wrong links

« Last post by gd_on on July 01, 2026, 04:02:22 pm »

Strangely, though both new links seems correct, a click on them opens my default browser (firefox), but the web page is not opened and title bar and page looks empty. But if I copy the link manually in my browser, it's OK.
More, same behaviour for the link in the configuration of cscope plugin.
Nevertheless, the link at the bottom of configuration of spellchecker plugin works, to help how to configure spellchecker.

Remark: It looks that the text which appears on the windows for cscope ans cppcheck is the text field in the wxs file, but the url field is empty, so it's why the link does not work. More, in that case, the displayed text should not be marked as translatable (with macro _())

7

Plugins development / Re: cppcheck/vera wrong links

« Last post by Miguel Gimenez on June 30, 2026, 05:30:20 pm »

Fixed in r13877, thanks for reporting.

8

Plugins development / cppcheck/vera wrong links

« Last post by gd_on on June 30, 2026, 02:28:40 pm »

Links indicated in cppcheck/vera plugin config are not correct. They do not work when I click on them.
For cppcheck, a good link could be https://cppcheck.sourceforge.io/ (with .io, not .net)
For vera, it looks it's no more available on bitbucket, but can be found on https://github.com/verateam/vera

9

Using Code::Blocks / Re: Error Running Any Code

« Last post by Miguel Gimenez on June 30, 2026, 10:54:54 am »

Follow these instructions.

10

Help / Re: Codeblocks + gcc

« Last post by ppnl on June 30, 2026, 01:06:40 am »

Yes, I found it. Thanks. It took a while because the "program files" folder has a space in the name. That isn't a valid path unless you enclose the name in quotes. Took some fumbling to figure what was going on.

Did somebody forget that in their automatic configuration tool?

And now for the hard part. Getting SFML to work with it.