Recent Posts

1

Using Code::Blocks / Re: Absolute Newby. Please Help

« Last post by Михаил Агарков on Today at 04:34:29 pm »

You need the wxWidgets SDK with the compiled binaries for your compiler.
I did it like this:

• Download the Windows installer from here.
• Compile it using these instructions with the compiler you're planning to use.
• After successful compilation, create the "wx" global variable where you specify the path to the wxWidgets folder (should contain folders like build, include, lib).
• Set the project configurations to be the same as what wxWidgets was compiled with (see screenshot)

Should work after that.

2

General (but related to Code::Blocks) / Re: Is there any plan to release a new version?

« Last post by Miguel Gimenez on June 26, 2026, 11:52:20 am »

Spam reported to moderator.

3

General (but related to Code::Blocks) / Re: Is there any plan to release a new version?

« Last post by jisoo200 on June 26, 2026, 09:15:12 am »

Thanks for sharing your insights on slope run! It really helped me understand the mechanics better. Grateful to be part of this community where we can learn and grow together!  slope run

4

Using Code::Blocks / Re: Absolute Newby. Please Help

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

Attach or post your compilation log in code tags (the # in the post creation window).

Use this instructions to generate it.

5

Using Code::Blocks / Absolute Newby. Please Help

« Last post by Petrus Vorster on June 24, 2026, 04:52:53 pm »

Greetings all
Never touched C++. Always on Powerbasic and Lazarus  Pascal.

Downloaded the codeblocks-25.03mingw-setup.exe and installed.
I assume this question has been posted a million times, but here goes.

I cant make nothing work. Installed WX widgets. That is about it.
I recon my links to resources and compilers etc is all wrong. (I did not see a default for dummies).

Nothing works. I can create a simple Dialog form, add a few buttons etc, but nothing will run. Everything is something.h not found in directory.

Please, lets consider me as rock bottom.
On a new project with one simple dialog e.g. Form1 what need to point where? What setting doe i need to have for global, what need to be set to make a simple project that will compile?

Sorry, I assume this is for advanced users, I just need to get the basics right first. Will ask lots of questions.

Many Thanks.

-Peter

6

Development / Re: wxSmith use bad constructor for wxStaticBoxSizer

« Last post by Miguel Gimenez on June 19, 2026, 10:33:01 am »

Spam reported to moderator.

7

Development / Re: wxSmith use bad constructor for wxStaticBoxSizer

« Last post by Justin975ht on June 19, 2026, 09:02:12 am »

The documentation hot games say that the child of a wxStaticBoxSizer should be the wxBoxSizer and not the owner of the wxStaticBoxSizer.
On Linux, for example, I can see the following warning on the console:
Element wxStaticText of wxStaticBoxSizer should be created as child of its wxStaticBox and not of wDialog.

I test several builder on a very simple case: a dialog window with a wxStaticBoxSizer that contain a wxStaticText and a wxTextCtrl.
With wxSmith:

DialogFormSmith::DialogFormSmith(wxWindow* parent,wxWindowID id)
{
    //(*Initialize(DialogFormSmith)
    wxStaticBoxSizer* StaticBoxSizer1;

    Create(parent, id, _("Test with wxSmith"), wxDefaultPosition, wxDefaultSize, wxDEFAULT_DIALOG_STYLE, _T("id"));
    StaticBoxSizer1 = new wxStaticBoxSizer(wxHORIZONTAL, this, _("StaticBoxSizer"));
    StaticText1 = new wxStaticText(this, wxID_ANY, _("Label"), wxDefaultPosition, wxDefaultSize, 0);
    StaticBoxSizer1->Add(StaticText1, 1, wxALL|wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL, 5);
    TextCtrl1 = new wxTextCtrl(this, wxID_ANY, _("Text"), wxDefaultPosition, wxDefaultSize, 0, wxDefaultValidator);
    StaticBoxSizer1->Add(TextCtrl1, 1, wxALL|wxALIGN_CENTER_HORIZONTAL|wxALIGN_CENTER_VERTICAL, 5);
    SetSizer(StaticBoxSizer1);
    StaticBoxSizer1->SetSizeHints(this);
    //*)
}

with wxFormBuilder:

DialogFormBuilder::DialogFormBuilder( wxWindow* parent, wxWindowID id, const wxString& title, const wxPoint& pos, const wxSize& size, long style ) : wxDialog( parent, id, title, pos, size, style )
{
   this->SetSizeHints( wxDefaultSize, wxDefaultSize );

   wxStaticBoxSizer* sbSizer1;
   sbSizer1 = new wxStaticBoxSizer( new wxStaticBox( this, wxID_ANY, _("StaticBoxSizer") ), wxHORIZONTAL );

   m_staticText1 = new wxStaticText( sbSizer1->GetStaticBox(), wxID_ANY, _("MyLabel"), wxDefaultPosition, wxDefaultSize, 0 );
   m_staticText1->Wrap( -1 );
   sbSizer1->Add( m_staticText1, 0, wxALL, 5 );

   m_textCtrl1 = new wxTextCtrl( sbSizer1->GetStaticBox(), wxID_ANY, wxEmptyString, wxDefaultPosition, wxDefaultSize, 0 );
   sbSizer1->Add( m_textCtrl1, 0, wxALL, 5 );


   this->SetSizer( sbSizer1 );
   this->Layout();
   sbSizer1->Fit( this );

   this->Centre( wxBOTH );
}

With wxGlade:

DialogFormGlade::DialogFormGlade(wxWindow* parent, wxWindowID id, const wxString& title, const wxPoint& pos, const wxSize& size, long style):
    wxDialog(parent, id, title, pos, size, wxDEFAULT_DIALOG_STYLE)
{
    // begin wxGlade: DialogFormGlade::DialogFormGlade
    SetTitle(wxT("Test with wxGlade"));
    wxStaticBoxSizer* sizer_1 = new wxStaticBoxSizer(new wxStaticBox(this, wxID_ANY, wxT("StaticBoxSizer")), wxHORIZONTAL);
    wxStaticText* label_1 = new wxStaticText(sizer_1->GetStaticBox(), wxID_ANY, wxT("Label"));
    sizer_1->Add(label_1, 0, 0, 0);
    text_ctrl_1 = new wxTextCtrl(sizer_1->GetStaticBox(), wxID_ANY, wxEmptyString);
    sizer_1->Add(text_ctrl_1, 0, 0, 0);

    SetSizer(sizer_1);
    sizer_1->Fit(this);
    Layout();
    // end wxGlade
}

The codes generated by wxFormBuilder and wxGlade are good: no warning.
I join a complete project for testing

It looks like wxSmith is generating incorrect parent-child relationships for controls inside wxStaticBoxSizer. Since wxFormBuilder and wxGlade correctly use GetStaticBox() as the parent and produce no warnings, this appears to be a wxSmith code generation issue that should be addressed in a future update.

8

Nightly builds / Re: The 27 May 2026 build (13855) is out.

« Last post by 20k on June 17, 2026, 10:27:58 pm »

[Main Instruction]
A debugging check in this application has failed.

I've found that deleting the .conf file just one time solved this for me.

Pecan, trying to re-customize my default.conf I think I found the root cause of the issue and so a quick way to fix it. The root cause of the debugging checks is a specific setting

Settings->Environment Settings->Notebooks Appearance->Tab Style

If you set the tab style to Firefox2 or Microsoft Visual Studio 7.1 the debugging checks are raised

Uisng default or Simple Tabs no debugging checks are raised.

So to me is enough to change my old settings from Firefox 2 to default to get a working default.conf (my old one). I hope this helps to understand how to fix the issue.

This didn't work for me (I'm experiencing the same problem), as my tabs were set to default already

9

General (but related to Code::Blocks) / Re: CodeBlocks on Linux

« Last post by christo on June 16, 2026, 09:32:35 pm »

Hi Miguel Gimenez, I've seen the hang when tested on Fedora 43 with 25.03. I think it is a good idea to provide a new release as it might be affecting lot of new distros.

Created appImage using svn revision 13865 and is available at https://github.com/josephch/codeblocks/releases/download/svn13865/CodeBlocks-r13865-x86_64.AppImage

Please give execution permission before execution.

Code

chmod +x ./CodeBlocks-r13865-x86_64.AppImage 
./CodeBlocks-r13865-x86_64.AppImage 

10

General (but related to Code::Blocks) / Re: CodeBlocks on Linux

« Last post by Miguel Gimenez on June 16, 2026, 07:48:41 pm »

I have tested the AppImage on Ubuntu 26.04, but C::B 25.03 has problems with libglycin (hang on startup due to wxSmith) and Wayland (unable to dock panes). Can you create an AppImage using the current trunk?

Thank you.