Recent Posts

21

Help / Re: Installing Code::Blocks from source on Linux

« Last post by christo on March 20, 2025, 05:51:31 pm »

@Miguel Gimenez I think above patch can cause compiling against astyle headers provided in codeblocks,  and link to astyle libraries present in the system. This might cause issues because of ABI incompatibility.

22

Plugins development / DevPak installer works?

« Last post by Михаил Агарков on March 20, 2025, 04:59:30 pm »

Does the DevPak installer still work to this day? It tries to connect to a now offline site and doesn't let the user change it.
If it works I think it should be patched to let the user type in a URL for any website for installation from it.

23

Nightly builds / Re: The 15 March 2025 build (13634) is out.

« Last post by ThierryD on March 20, 2025, 02:24:34 pm »

Hello Xaviou,

Nigthly build SVN 13634 seems inaccessible on your PPA.
On my two config Linux Mint 22.1 (~ Ubuntu Noble 24.04), travel into PPA look only SVN 13620.

Thank's.

Thierry.

24

Help / Re: Installing Code::Blocks from source on Linux

« Last post by Miguel Gimenez on March 20, 2025, 12:04:14 pm »

Angle brackets changed to double quotes in r13635, thank you for reporting.

25

Help / Re: Installing Code::Blocks from source on Linux

« Last post by Krice on March 20, 2025, 10:35:20 am »

Fixed astyle by searching which files were including astyle.h with angle brackets, there are three headers in astyle directory: asstreamiterator.h, dlgformattersettings.h and formattersettings.h. Changed those to "astyle/astyle.h" which seemed like what they should be in the first place, because now they are using the astyle that is in the plugin directory.

I still got wx errors after that so I thought why not compile wx from the source, because it seems to want to use the usr/local version anyway. Wx compiled without errors which means I must have compiled it earlier. Then sudo make install and that was it. Code::Blocks compiled after that.

I don't know if this is supposed to happen, but the new Code::Blocks overwrites the one installed from Fedora Software, because when you click the icon it runs the new version.

26

Help / Re: Installing Code::Blocks from source on Linux

« Last post by stahta01 on March 19, 2025, 05:34:27 pm »

If I remember correctly, "AX_CXX_COMPILE_STDCXX(17, noext)" will result in wxSmith not building.

Tim S.

27

Nightly builds / Re: The 15 March 2025 build (13634) is out.

« Last post by christo on March 19, 2025, 04:42:22 pm »

I had a similar problem in the past after installing a custom version of libtool.
One quick thing to test :  Look for file  wxwin.m4  and add that path to ACLOCAL_FLAGS. For example, I have wxwin.m4 in /usr/local/share/aclocal , so I run below command.

Code

ACLOCAL_FLAGS="-I /usr/local/share/aclocal" ./bootstrap

Hope this helps

28

Nightly builds / Re: The 15 March 2025 build (13634) is out.

« Last post by Miguel Gimenez on March 19, 2025, 01:32:06 pm »

THe same problem was asked in this solved post, hope it helps.

29

Help / Re: Installing Code::Blocks from source on Linux

« Last post by christo on March 19, 2025, 01:20:29 pm »

In some unrelated projects people have solved this by creating a symlink to libtiff which in this case is libtiff.so.6.0.2 (other files are symlinks themselves) so I did that in my usr/lib64, but now it's just giving an error already in the compile phase, in astyle.h:

Code

In file included from asstreamiterator.h:15,
                 from asstreamiterator.cpp:10:
/usr/include/astyle.h:295:44: error: 'std::string_view' has not been declared
  295 |         const std::string* findHeader(std::string_view line, int i,
      |                                            ^~~~~~~~~~~

This seems to indicate that something doesn't include std::string header, right?

Edit: also, there could be some kind of confusion in including astyle.h in asstreamiterator.h. If you use angle brackets it's trying to find the file in usr/library while there is also plugins/astyle/astyle directory where you can find another astyle.h which is not included unless you write #include "astyle/astyle.h", well I guess depending how this project is handling that kind of stuff, could be something else happening.

This is because if astyle is installed in the PC,  codeblocks uses it instead of that in sdk. Astyle installed in your PC is new and uses c++17 features, but codeblocks still uses c++11 flags. That is why compilation fails.

You can try following patch

Code

diff --git a/configure.ac b/configure.ac
index 1d4898a28..b8ed0b7cf 100644
--- a/configure.ac
+++ b/configure.ac
@@ -361,7 +361,7 @@ CPPFLAGS="$CPPFLAGS -DPIC $CB_TINYXML_CFLAGS"
 CXXFLAGS="$CXXFLAGS $PIC_CFLAGS -fexceptions"
 AC_SUBST(codeblocks_PCH_FLAGS, "$PCH_FLAGS")
 
-AX_CXX_COMPILE_STDCXX(11, noext)
+AX_CXX_COMPILE_STDCXX(17, noext)
 
 dnl AM_PATH_GTK(1.2.7, ,
 dnl             AC_MSG_ERROR(Cannot find GTK: Is gtk-config in path?),

30

Nightly builds / Re: The 15 March 2025 build (13634) is out.

« Last post by Bug Killer on March 19, 2025, 01:13:31 pm »

I cant build rev 13634 on AlmaLinux 9 because something goes wrong in bootstrap. I didn't try to build since 13586. wxWidgets version is 3.2.6.

Code

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:139: warning: macro 'AM_OPTIONS_WXCONFIG' not found in library
configure.ac:140: warning: macro 'AM_PATH_WXCONFIG' not found in library
configure.ac:26: installing './compile'
configure.ac:7: installing './config.guess'
configure.ac:7: installing './config.sub'
configure.ac:22: installing './install-sh'
configure.ac:22: installing './missing'
src/base/tinyxml/Makefile.am: installing './depcomp'
configure.ac:139: error: possibly undefined macro: AM_OPTIONS_WXCONFIG
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:140: error: possibly undefined macro: AM_PATH_WXCONFIG