Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
Via github it was relatively easy to find that the following commit reverted it:
https://github.com/arnholm/codeblocks_sfmirror/commit/2cc176ba23528185ca18d5377510b64e7a81b38f#diff-4007afe15336751ba46fee72ba5ed7002efc465819b8384b5b0fb76edfd41741R394-R1570

The comment/svn reference is:
- Clangd_client Remove dead/unused code, no additions or code changes
git-svn-id: https://svn.code.sf.net/p/codeblocks/code/trunk@13636 2a5c6006-c6dd-42ca-98ab-0921f2732cef

I do not use SVN and find the github repo allot easier to use to find things.
2
This was fixed six hours ago by r13622.

The fixed has gone missing, I think.

Tim S.
3
Help / Re: Installing Code::Blocks from source on Linux
« Last post by christo on Yesterday at 05:30:34 pm »
@Miguel Gimenez

I tested the change and it did not work.

Looks like a simple solution is just to move AX_CXX_COMPILE_STDCXX before checking astyle, then it will discard installed astyle if not supported. Please see configure logs with latest astyle below.
Code
checking astyle.h usability... no
checking astyle.h presence... yes
configure: WARNING: astyle.h: present but cannot be compiled
configure: WARNING: astyle.h:     check for missing prerequisite headers?
configure: WARNING: astyle.h: see the Autoconf documentation
configure: WARNING: astyle.h:     section "Present But Cannot Be Compiled"
configure: WARNING: astyle.h: proceeding with the compiler's result
checking for astyle.h... no

I tested the change with an older version of astyle, which does not require c++17 ( v 3.4.14), and it selects the installed astyle
Code
checking astyle.h usability... yes
checking astyle.h presence... yes
checking for astyle.h... yes
checking for astyle::ASPeekStream... yes

Im no expert in autotools, but this looks like a harmless change. Attaching the patch.
4
Help / Re: Installing Code::Blocks from source on Linux
« Last post by Miguel Gimenez on Yesterday at 01:06:43 pm »
This code in configure.ac:88 should work:
Code
if test "$HAVE_ASTYLE" = "yes" -a "$HAVE_CXX11" != "1" -a "$HAVE_CXX14" != "1" ; then
AC_CHECK_TYPE([astyle::ASPeekStream], , [HAVE_ASTYLE=no], [#include "astyle.h"])
else
HAVE_ASTYLE=no
fi
Looking for HAVE_CXX11 usage examples I have seen comparations with "1", "yes" and "TRUE", GNU uses "1".
5
Nightly builds / Re: The 15 March 2025 build (13634) is out.
« Last post by Bug Killer on Yesterday at 11:20:16 am »
Code::Blocks 13634, wxWidgets 3.2.6 and wxSQlite 3.2.2.1 RPMs for RHEL 9 and derivatives are available from my signed repository https://www.theox.net/codeblocks.
6
General (but related to Code::Blocks) / FYI: wxWidgets 3.2.7 Released
« Last post by ollydbg on Yesterday at 10:57:54 am »
7
Help / Re: Installing Code::Blocks from source on Linux
« Last post by Krice on Yesterday at 09:56:05 am »
Yeah, I don't actually know how that worked, because doesn't it also need the library file? Maybe just building wx from source fixed everything. I guess I could try it again by using angle brackets and rebuilding Code::Blocks, but I'm not in the mood right now. Anyway, when you are using angle brackets you should somehow make sure it's using headers in the project (and not in lib or elsewhere in path), because why would you otherwise have them in a project directory? And even then it feels wrong, because two styles of using #include are there for a reason.
8
Help / Re: Installing Code::Blocks from source on Linux
« Last post by Miguel Gimenez on Yesterday at 09:16:40 am »
Reverted commit 13635.
9
Help / Re: Installing Code::Blocks from source on Linux
« Last post by stahta01 on March 20, 2025, 10:24:16 pm »
Is there a HAVE_CXX17?

EDIT: I do not use autotools, if someone can post a patch for configure.ac or Makefile.am including checking for C++17 it would be safer.

Then you would have to keep editing the configure.ac each time a new version is released; so now HAVE_CXX17, HAVE_CXX20, and HAVE_CXX23.

Tim S.

Likely best to wait till a person who is more of an expert can do the change.

Tim S.
10
Help / Re: Installing Code::Blocks from source on Linux
« Last post by stahta01 on March 20, 2025, 10:21:26 pm »
Is there a HAVE_CXX17?

EDIT: I do not use autotools, if someone can post a patch for configure.ac or Makefile.am including checking for C++17 it would be safer.

Then you would have to keep editing the configure.ac each time a new version is released; so now HAVE_CXX17, HAVE_CXX20, and HAVE_CXX23.

Tim S.
Pages: [1] 2 3 4 5 6 ... 10