Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
Help / Re: codeblocks c++ thread
« Last post by MortenMacFly on Today at 05:29:29 am »
This should help:,9996.0.html
...this is true.

Please ask such questions not in the forum that is dedicated to the development of the IDE "Code::Blocks" but in a standard C/C++ forum.

Topic locked.
Help / Re: codeblocks c++ thread
« Last post by Commaster on Yesterday at 09:01:45 pm »
Help / codeblocks c++ thread
« Last post by Salih2003 on Yesterday at 02:41:55 pm »
Hello. I was learning the thread library of c++. I wrote a code like this.
#include <iostream>
#include <thread>
#include <clocale>
using namespace std;

void print(string message)
    cout << message << endl;

int main()
    thread th1(print,"test");
    return 0;

C++17 flag is raised. However, I am getting an error like this:

||==== Build: Debug in console (compiler: GNU GCC Compiler) ===|
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\CodeBlocks\console\main.cpp||In function 'int main()':|
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\CodeBlocks\console\main.cpp|14|error: 'thread' was not declared in this scope|
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\CodeBlocks\console\main.cpp|4|note: 'std::thread' is defined in header '<thread>'; did you forget to '#include <thread>'?|
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\CodeBlocks\console\main.cpp|17|error: 'th' was not declared in this scope; did you mean 'tm'?|
||==== Build failed: 2 error(s), 0 warning(s) (0 minute(s), 0 second(s)) ===

Why is this problem?
my computer system:
intel core i2 duo 32bit
3gb ram
windows 7
GPU: none.
Since I don't know English, I used google translate.
Development / Re: C::B Github Actions build information
« Last post by AndrewCot on Yesterday at 08:13:21 am »
I have enabled issues and discussions.
I have been fighting the Windows github actions for days now and have made allot of progress, but have not got C::B building.

The wxWidget build script has a work around for a bug in wxWidget where it does not create the /lib/gcc_dll/mswu/wx directory if -j is not 0 when doing the "mingw32-make.... setup.h" step. I have raised an issue (, but it was closed as it was a dup of 14470 that has been open since 2012!!!! yes 10 years old and a such I do not think it will get fixed.
The bash scripts have a allot of error checking, but could be re-worked to move code into functions to make it more maintainable.
Once I have the workflow building C::B I will then post that it is building. I will then need to look at the next stage of packaging the build (for Linux, MacOS and Windows) and then saving the artifacts (results). I will only package and upload the artifacts on a Git tag.
Development / Re: C::B Github Actions build information
« Last post by ollydbg on Yesterday at 07:49:02 am »
Nice work!

But this is a complex task for me.  :(

Can you open the issue system in your git repo:  acotty/CodeBlocks_Unofficial_Testing: Unofficial GIT clone of C::B repo in SourceForge (maintained by C::B developer, accepts patches or pull requests)

So that people can discussion issues here.

Once you have finished the Windows build action tweaks, I will fork and try it.  ;)
Plugins development / Re: 'Collector' plugin
« Last post by ollydbg on Yesterday at 07:19:55 am »
Nice work!
Development / Re: C::B Github Actions build information
« Last post by AndrewCot on Yesterday at 06:14:32 am »
If you need to work on Github actions then you may want to check out the following repo as it allows you to test the workflow and steps on your PC instead of github:
In order to checkout wxwidgets repo you will need to do the following:
a) Create a a Personal Access Token
b) Create a .secrets file with the following line in it:

  • GITHUB_TOKEN=replaceThisTextWithYourPersonalAccessToken
The following is the command line I have been using to test the Windows workflow on my Windows 10 PC from a windows command prompt:
  • .\bin\Runner.Client.exe --workflow .github\workflows\Windows-continuous-integration.yml --event push --payload CB_test.json -P windows-2019=-self-hosted
The CB_test.json file is:
    "inputs": {
        "x": "Hello World from event"
Development / Re: New Variable to support wx-config in MSys2 MinGW
« Last post by ollydbg on Yesterday at 05:20:03 am »
Hi, tim, I add this macro in rev12816. Thanks!
Plugins development / 'Collector' plugin
« Last post by LETARTARE on Yesterday at 01:39:12 am »
Hello everyone,
I suggest a plugin for translate project using 'Code::Blocks'.
This extension of  'Code::Blocks' will be offered on:
Development / Re: New Variable to support wx-config in MSys2 MinGW
« Last post by PB on May 20, 2022, 11:52:17 pm »

Summary of the current changes
Redo manifest filename logic in "wx/msw/wx.rc".
The prior manifest logic failed to work under Clang64.

I know virtually nothing about MSYS2 packages but I wonder why are those changes necessary?

I have tried not that long ago and wxWidgets with the unmodified wx.rc builds just fine not only with GCC (package mingw-w64-x86_64-toolchain) but also clang (package mingw-w64-clang-x86_64-toolchain)?

Is there another clang package? I admit I have no idea if that package i listed uses its own resource compiler (llvm-rc) or mingw one (windres).
Pages: [1] 2 3 4 5 6 ... 10