41
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.
Tim S.
News:
Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!
Recent Posts
42
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.
Hope this helps
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
43
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.
44
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:CodeIn 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?),
45
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
46
General (but related to Code::Blocks) / Re: Welcome Newcomers - PLEASE READ!!!
« Last post by Karl on March 19, 2025, 12:31:22 pm »Hello,
it's me and I am a real human.
I'm trying to learn more about C++. Already got a lot of books but of course I need a compiler and an environment, Code::Blocks seems to be best option.
Until now no problems with Code::Blocks, but running in some problems with the language support of mingw. But this belongs to another section of the board.
btw: My parents language is German.
it's me and I am a real human.
I'm trying to learn more about C++. Already got a lot of books but of course I need a compiler and an environment, Code::Blocks seems to be best option.
Until now no problems with Code::Blocks, but running in some problems with the language support of mingw. But this belongs to another section of the board.
btw: My parents language is German.
47
Help / Re: Installing Code::Blocks from source on Linux
« Last post by Krice on March 19, 2025, 09:38:41 am »I could have compiled wx from source but there was no source directory. Downloaded wx source, ran configure and then make uninstall. But it doesn't help. I think it did remove something from usr/local/lib, but it left wx directory with another empty wx directory at the end of it. wx can be also found from usr/lib64 and /lib64. How does it confuse compiler if it's installed in those locations, shouldn't the compiler choose one and not mix them, which could cause some problems? At this point I probably have to delete package wx, see if anything is left and delete those files manually, then reinstall it. Right? F-- linux...
48
Help / Re: Installing Code::Blocks from source on Linux
« Last post by stahta01 on March 19, 2025, 12:53:56 am »it shows what package you need to have installed
Am I supposed to know how to read that? I think compiler errors could also hint that wxWidgets is missing, but it should be installed... Maybe I could try to write a wx program to see if it works. Anyway, how is this so difficult? I think this is more difficult than when I tried to compile Code::Blocks in OSX and that was a journey.
The [linking] error posted implied wxWidgets was from an local build instead of being an Linux Distro package.
Did you build it recently? If yes, I have nothing to suggest. If no, I suggest building it again and see if the error changes or goes away.
And, the posting the reason you did the local build of wxWidgets might help people to help you.
Tim S.
49
Help / Re: Installing Code::Blocks from source on Linux
« Last post by Krice on March 18, 2025, 07:18:36 pm »it shows what package you need to have installed
Am I supposed to know how to read that? I think compiler errors could also hint that wxWidgets is missing, but it should be installed... Maybe I could try to write a wx program to see if it works. Anyway, how is this so difficult? I think this is more difficult than when I tried to compile Code::Blocks in OSX and that was a journey.
50
Help / Re: Installing Code::Blocks from source on Linux
« Last post by SharkCZ on March 17, 2025, 04:30:29 pm »You can get the latest nightly C::B for Fedora from https://copr.fedorainfracloud.org/coprs/sharkcz/danny/. As for the build procedure you can take a look at the spec file, it shows what package you need to have installed and what commands to run, see https://src.fedoraproject.org/rpms/codeblocks/blob/rawhide/f/codeblocks.spec