Recent Posts

1

Using Code::Blocks / Re: how to let github action to run codeblocks.exe to build cbp project

« Last post by ollydbg on Yesterday at 05:36:33 pm »

https://github.com/asmwarrior/image-label-gui/actions/runs/36323032087

This is my recent progress. I use cbp2make to generate a makefile from cbp, and later build the makefile.

2

Nightly builds / Re: The 06 September 2026 build (14003) is out.

« Last post by luisalberto on Yesterday at 03:59:05 pm »

I don't know if I can say it here but every time I am using CodeBlocks the wxSmiths tools Icons are nearly hidden by the Horizontal ScrollBar. Windows 11 25H2. I have to go to Settings->Editor->WxSmiths and make tool Icons small to make them visible. Please can this be solved? Thanks fro the great tool that is CodeBlocks.

3

Using Code::Blocks / Re: Perfomance question: CodeBlocks "normal" RAM usage and file closing delay

« Last post by CH4Code on Yesterday at 11:22:02 am »

Hello,

I managed to solve all the problems, I'll post the solution in case someone else stumbles into this:

The problems (high memory usage and 10 second file closing delay) were solved after I checked the CB startup logs (In-IDE unter Logs&Others pane -> Code::Blocks tab) and fixed any problems appearing there:

I fixed the help.ini file which pointed to the wrong help file .chm file names (I dont think this was related to the performance hits).

I fixed some paths C:\Users\<myUser>\AppData\Roaming\CodeBlocks\default.conf which where WRONG and from my old installation of CB 2020.
Especially SpellChecker plugin had some missing icons due to outdated path. Also the sets>gcc>master_path>str compiler had the wrong path (I'm not using it, I'm using a msys2-mingw compiler so I did not notice it was defunct). Finally I added a .idx and .dat thesaurus file for SpellChecker, like described in the spell checker Wiki.

After these measures now CB only requires 80MB of memory after starting and about 100MB after I load my project, and closing files only takes a split second instead of 10 seconds.I'm not sure which of the problems caused the memory hogging, but one of those must have been it.

I'm quite happy now for me this is solved.

I dont think CB should react to incorrect paths in this manner, so if some of the plugin developers of SpellChecker or CB developers may want to have a look how this can happen.

Cheers

4

Development / Re: cbp2make does not contain a Makefile.am?

« Last post by Wkerry on Yesterday at 10:02:03 am »

Try this:
https://github.com/stahta01/CodeBlocks_Unofficial_Testing/blob/master/src/tools/cbp2make/Makefile.am

5

Development / cbp2make does not contain a Makefile.am?

« Last post by ollydbg on Yesterday at 06:18:49 am »

Hi, when I looked at the

https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-codeblocks/PKGBUILD

I see such code snippet:

Code

  cp -R ${srcdir}/${_realname}_${pkgver}/src/tools/cbp2make/ "${srcdir}"/build-${MSYSTEM}/
  cd "${srcdir}"/build-${MSYSTEM}/cbp2make
  if check_option "debug" "n"; then
    make CC=${CC} CXX=${CXX} LD=${CXX} --jobs=1 -f cbp2make.cbp.mak.unix release
  else
    make CC=${CC} CXX=${CXX} LD=${CXX} --jobs=1 -f cbp2make.cbp.mak.unix debug
  fi

So, do we need to add a Makefile.am?

I see other tools in this folder:  src/tools, such as src/tools/cb_share_config and src/tools/CBLauncher, they all have a Makefile.am, but why cbp2make does not?

Thanks.

6

Using Code::Blocks / Re: Does CB Nightly debugger plugin work with parameters?

« Last post by Pecan on September 26, 2026, 07:20:38 pm »

Thanks for the answer; so, it is likely working and it is user error on my part.

Tim S.

Turn on Debugger "Full Log" in MainMenu/Settings/Debugger/Common to see what the debugger plugin did with your arguments.

7

Using Code::Blocks / Re: Does CB Nightly debugger plugin work with parameters?

« Last post by stahta01 on September 26, 2026, 04:39:44 pm »

Thanks for the answer; so, it is likely working and it is user error on my part.

Tim S.

8

Help / Re: wxSmith has a blackout!

« Last post by Danois on September 26, 2026, 12:04:28 pm »

Just to make sure that this was not a fluke, I tested it again by running the command "sudo apt remove -y pgkconf pkg-config" which also removed the following dependent packages, some of which are required to build C::B:

Code

REMOVING:
  libatk-bridge2.0-dev  libdbus-1-dev          libglycin-2-dev  libxft-dev
  libatk1.0-dev         libfontconfig-dev      libgtk-3-dev     pkgconf
  libatspi2.0-dev       libgdk-pixbuf-2.0-dev  libharfbuzz-dev
  libcairo2-dev         libgio-2.0-dev         libpango1.0-dev
  libdatrie-dev         libglib2.0-dev         libthai-dev

Then I ran "./bootstrap" which produced the following output:

Code

Using 'svn --xml info' to get the revision
Found revision: '14038' '2026-09-21 09:14:07'
removed [* 190 files *]
Note: If you want to build debian packages you have to first run the debian/setup_control.sh script. See the script for details how to use it.
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:27: installing './compile'
configure.ac:23: installing './missing'
src/base/tinyxml/Makefile.am: installing './depcomp'
configure.ac:21: warning: The macro 'AC_HELP_STRING' is obsolete.
configure.ac:21: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
./lib/autoconf/general.m4:1534: AC_ARG_ENABLE is expanded from...
m4/acinclude.m4:87: CODEBLOCKS_CHECK_DEBUG is expanded from...
configure.ac:21: the top level
configure.ac:32: warning: The macro 'AC_CONFIG_HEADER' is obsolete.
configure.ac:32: You should run autoupdate.
./lib/autoconf/status.m4:719: AC_CONFIG_HEADER is expanded from...
configure.ac:32: the top level
configure.ac:57: warning: The macro 'AC_HEADER_STDC' is obsolete.
configure.ac:57: You should run autoupdate.
./lib/autoconf/headers.m4:663: AC_HEADER_STDC is expanded from...
configure.ac:57: the top level
configure.ac:65: warning: The macro 'AC_HEADER_TIME' is obsolete.
configure.ac:65: You should run autoupdate.
./lib/autoconf/headers.m4:702: AC_HEADER_TIME is expanded from...
configure.ac:65: the top level
configure.ac:82: warning: The macro 'AC_HELP_STRING' is obsolete.
configure.ac:82: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
./lib/autoconf/general.m4:1534: AC_ARG_ENABLE is expanded from...
configure.ac:82: the top level
configure.ac:173: warning: The macro 'AC_HELP_STRING' is obsolete.
configure.ac:173: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
m4/acinclude.m4:4: CODEBLOCKS_GET_PLATFORM is expanded from...
configure.ac:173: the top level
configure.ac:174: warning: The macro 'AC_HELP_STRING' is obsolete.
configure.ac:174: You should run autoupdate.
./lib/autoconf/general.m4:204: AC_HELP_STRING is expanded from...
./lib/autoconf/general.m4:1534: AC_ARG_ENABLE is expanded from...
m4/acinclude.m4:136: CODEBLOCKS_ENABLE_SETTINGS is expanded from...
configure.ac:174: the top level
configure.ac:174: warning: The macro 'AC_TRY_COMPILE' is obsolete.
configure.ac:174: You should run autoupdate.
./lib/autoconf/general.m4:2845: AC_TRY_COMPILE is expanded from...
m4/acinclude.m4:136: CODEBLOCKS_ENABLE_SETTINGS is expanded from...
configure.ac:174: the top level

Finally I ran the command "./configure --with-contrib-plugins=all,-NassiShneiderman --prefix=/opt/codeblocks" which gave the following output:

Code

checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking whether configure should try to set CFLAGS/CXXFLAGS/CPPFLAGS/LDFLAGS... yes
checking whether to enable debugging... no
checking for a BSD-compatible install... /usr/bin/install -c
checking whether sleep supports fractional seconds... yes
checking filesystem timestamp resolution... 0.01
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking xargs -n works... yes
checking how to create a ustar tar archive... gnutar
checking whether make supports the include directive... yes (GNU style)
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for x86_64-pc-linux-gnu-gcc... no
checking for gcc... gcc
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether the compiler supports GNU C++... yes
checking whether g++ accepts -g... yes
checking for g++ option to enable C++11 features... none needed
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for x86_64-pc-linux-gnu-g++... no
checking for x86_64-pc-linux-gnu-c++... no
checking for x86_64-pc-linux-gnu-gpp... no
checking for x86_64-pc-linux-gnu-aCC... no
checking for x86_64-pc-linux-gnu-CC... no
checking for x86_64-pc-linux-gnu-cxx... no
checking for x86_64-pc-linux-gnu-cc++... no
checking for x86_64-pc-linux-gnu-cl.exe... no
checking for x86_64-pc-linux-gnu-FCC... no
checking for x86_64-pc-linux-gnu-KCC... no
checking for x86_64-pc-linux-gnu-RCC... no
checking for x86_64-pc-linux-gnu-xlC_r... no
checking for x86_64-pc-linux-gnu-xlC... no
checking for x86_64-pc-linux-gnu-clang++... no
checking for g++... g++
checking whether the compiler supports GNU C++... (cached) yes
checking whether g++ accepts -g... yes
checking for g++ option to enable C++11 features... (cached) none needed
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/x86_64-linux-gnu-ld
checking if the linker (/usr/bin/x86_64-linux-gnu-ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/x86_64-linux-gnu-ld option to reload object files... -r
checking for file... file
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ranlib... ranlib
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... mt
checking if mt is a manifest tool... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for sys/time.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/x86_64-linux-gnu-ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/x86_64-linux-gnu-ld -m elf_x86_64
checking if the linker (/usr/bin/x86_64-linux-gnu-ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/x86_64-linux-gnu-ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/x86_64-linux-gnu-ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether the compiler supports GNU C++... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking for g++ option to enable C++11 features... (cached) none needed
checking dependency style of g++... (cached) gcc3
checking how to run the C preprocessor... gcc -E
checking for gcc... (cached) gcc
checking whether the compiler supports GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to enable C11 features... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) gcc3
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking for gawk... (cached) mawk
checking whether g++ supports C++17 features with -std=c++17... yes
checking whether the linker accepts -Wl,--no-undefined... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for egrep... (cached) /usr/bin/grep -E
checking for fcntl.h... yes
checking for limits.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for sys/param.h... yes
checking for unistd.h... (cached) yes
checking for malloc.h... yes
checking for sys/malloc.h... no
checking for malloc/malloc.h... no
checking for _Bool... yes
checking for stdbool.h that conforms to C99 or later... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for size_t... yes
checking for working volatile... yes
checking whether closedir returns void... no
checking for GNU libc compatible malloc... yes
checking for working memcmp... yes
checking whether lstat correctly handles trailing slash... yes
checking whether stat accepts an empty string... no
checking for vprintf... yes
checking for atexit... yes
checking for getcwd... yes
checking for isascii... yes
checking for memchr... yes
checking for memmove... yes
checking for memset... yes
checking for strcasecmp... yes
checking for strchr... yes
checking for strcspn... yes
checking for strdup... yes
checking for strrchr... yes
checking for strstr... yes
checking for dlopen in -ldl... yes
checking for pthread_create in -lpthread... yes
checking for snprintf... yes
checking for vsnprintf... yes
checking whether to disable system libraries and use bundled libraries... no
./configure: line 25601: syntax error near unexpected token `zlib,'
./configure: line 25601: `      PKG_CHECK_MODULES(zlib, zlib, HAVE_ZLIB=yes, HAVE_ZLIB=no)'

Because the existence of "pkg-config" is actually tested during a successful "./configure ..", as shown earlier, I assume that the macro "PKG_CHECK_MODULES( .. )" is used before the existence "pkg-config" is checked.

If I at this state run the command "sudo apt install pkg-config", and then re-run "./configure .." the error is still present and I have to run "./bootstrap" (or "autoreconf -if") to fix the issue.

I think that the check for "pkg-config" should be done earlier during "./configure .. ", and if not found user must be instructed to re-run "./bootstrap" after installing it.

I hope this helps and clarifies things! :-)

9

General (but related to Code::Blocks) / Re: github action [Resolved]

« Last post by ollydbg on September 26, 2026, 09:50:25 am »

Hi, jarod42, I'm currently having a similar github action issue in the Windows platform, see this post:

how to let github action to run codeblocks.exe to build cbp project

Can you have a look.

It looks like your project is still actively maintained, but your project is for linux system?

Thanks.

10

Using Code::Blocks / Re: how to let github action to run codeblocks.exe to build cbp project

« Last post by ollydbg on September 26, 2026, 09:48:17 am »

Probably the "Select default compiler" dialog...

Yes, is it possible to supply a dummy/default default.conf file for the codeblocks.exe to run? So that it use the default msys2's gcc compiler path.

From this project:

Jarod42/premake-sample-projects: Premake sample projects to easily test generators

I see a sample(default) configure file is supplied for codeblocks.