The 10 December 2022 build (13107) is out.

[killerbot]

We switched to wx 3.2.1 (on 01 October 2022) --> download the new wx dll's see link below

Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works.

A link to the unicode windows wxWidget dll(s) for Code::Blocks : https://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw32u_gcc_cb_wx321_2D_gcc810-mingw64.7z
A link to Mingw64 dll's needed by Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/Mingw64dlls8.1.0.7z


The 10 December 2022 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2022/CB_20221210_rev13107_win64.7z
  - Linux :
   none

The current SDK version is : 2.23.0

Resolved Fixed:

• Add support for riscv64 build on Linux (thanks vimer).
• Make translatable strings more translation-friendly.
• wxWidgets wizard: Add wx3.3 and make it translatable.
• Scripted Wizard: Make wizards (A to M) translatable.
• Scripted Wizard: Make wizards (N to Z and common) translatable.
• DefaultMimeHandler: Add warning to description about disabling it (ticket #1325).
• Show translated plugin titles and descriptions in menus and help.
• Plugin configuration dialog: Show translated strings.
• DragScroll - version 1.3.31 2022/11/12 - For focus-follows-mouse option, give focus to window with mouse movement; Allows log windows to re-click and scroll just by moving the mouse inside the log window; esp. useful after a click in a log window has moved the focus to an editor.
• clangd_client - Plugin for clangd on Windows, Linux, and Mac
• Scripted Wizard: Make new wxWidgets projects DPI-aware on MSW.
• New project dialog: Fix title.
• sdk: When the personality is "debug-plugin", we only load limited plugins
• sdk: adjust the parsing method of the text pipe chars to support both UTF-8 and other encoding text
• clangd_client 0.2.52 2022/11/19 Add cbAssertNonFatal() call to protocol.h work-around. Change .cbp(s) to -std=c++11 instead of c++17. This allows debian builds for CB (which does not support c++17). Thanks Andrew.
• ccManager.cpp Allow tooltips to be shown as unsorted content
• clangd_client 1.2.55 2022/11/23
• modernise/update crash handler dll (exchndl) from v0.9.1 to v0.9.7 (Windows only change)
• Remove CR from all plugin fields meant to be translated (ticket #1338).

Regressions/Confirmed/Annoying/Common bugs:

[Xaviou]

Hi.

Build on Debian failed : I've attached the build log.
It appens on Debian 11, on both 32 and 64 bits.

I didn't made the test on Debian 10

Regards
Xav'

[Miguel Gimenez]

That manifest.xml was removed in r13088, the Makefile.am was modified accordingly but may be something has been left over (or configure must be run again, I do not use autotools).

EDIT: Both Makefile.am must be modified so the zip is created with the manifest.xml from the plugin's root folder (patches welcome).

[Pecan]

Codesnippets re-commited (thus rev 13088 is reverted) so  that Debian builds work.

[gd_on]

Nevertheless, there is something wrong somewhere, because codesnippets has again 2 manifest.xml files, in 2 directories. And their contents are not exactly the same! (At least link to the wiki with https/http)

[Pecan]

Nevertheless, there is something wrong somewhere, because codesnippets has again 2 manifest.xml files, in 2 directories. And their contents are not exactly the same! (At least link to the wiki with https/http)

Thanks
I'll have a look at it as soon as I can crawl out from under clangd_client and DAP debugger.

[Frank_CB]

Have built a 64-bit version of C::B from SVN r13111 source, but am having troubles invoking the clangd_client plugin. Clangd_client had been added to SVN source sometime prior to r13106 (Thank you, Pecan).

After disabling code_completion in Plugin Manager and enabling clangd_client, a message is displayed stating that a compiler needs to be selected and than C::B needs to be restarted. MSVC 64-bit compiler is already selected. Clangd_ciient is no longer represented in settings>editor navigation sidebar either. Nightly 13107 is behaving the same way.

Any ideas as to why trying to invoke clangd_cieent is behaving this way?

[Pecan]

Have built a 64-bit version of C::B from SVN r13111 source, but am having troubles invoking the clangd_client plugin. Clangd_client had been added to SVN source sometime prior to r13106 (Thank you, Pecan).

After disabling code_completion in Plugin Manager and enabling clangd_client, a message is displayed stating that a compiler needs to be selected and than C::B needs to be restarted. MSVC 64-bit compiler is already selected. Clangd_ciient is no longer represented in settings>editor navigation sidebar either. Nightly 13107 is behaving the same way.

Any ideas as to why trying to invoke clangd_cieent is behaving this way?

Are you sure it was asking for a compiler?
If so, what was the actual message?

I suspect it's asking for the location of clangd.exe .
Clangd_client needs the clangd server location which does all the analysis work.
Clangd_client just passes messages back and forth to the language server called "clangd" or "clangd.exe"

See:
https://wiki.codeblocks.org/index.php/CB_Clangd_Client
for instructions how to install clangd.

[jdx]

1. Why do you still use ancient gcc 8.1? On Windows it has rather serious bug which has been fixed in 8.3 - see at the bottom of https://gcc.gnu.org/gcc-8/changes.html. For this reason a few years ago I lost some time when I was building Qt.
2. Why are there static libs in the nightly build archives? They seem to be redundant.

[ollydbg]

1. Why do you still use ancient gcc 8.1? On Windows it has rather serious bug which has been fixed in 8.3 - see at the bottom of https://gcc.gnu.org/gcc-8/changes.html. For this reason a few years ago I lost some time when I was building Qt.

I don't know, maybe killerbot(our dev) thought it was more stable.
For me, I use the latest gcc from msys2(mingw-w64 x86_64).

2. Why are there static libs in the nightly build archives? They seem to be redundant.

Do you mean the .a files, I think they are basically not needed.

[Pecan]

2. Why are there static libs in the nightly build archives? They seem to be redundant.

Do you mean the .a files, I think they are basically not needed.

Historically they weren't included in the the nightly, but were put there by request so users could build plugins without building all of CodeBlocks.
The user only had to copy the nightly .../src folder and use the wxWidgets provided by their OS distribution, then link with the .a files.