The 12 February 2023 build (13205) 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 12 Februari 2023 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2023/CB_20230212_rev13205_win64.7z
  - Linux :
   none

The current SDK version is : 2.24.0

Resolved Fixed:

• Clangd-client: Fix HiDPI for wxWidgets >= 3.1.6.
• src: Implement scrolling project tree while dragging items (fix ticket #1356)
• Fix renaming virtual folders (ticket #1371).
• wxSmith: Fix compiling wxsDateTimePickerCtrl with makefile on linux (thanks Bug Killer)
• Make disabling I18n in wxSmith really work (thanks Bug Killer).
• Add UI for automatic source folders aka project globs
• clangd plugin: don't crash C::B hard when trying to use std::stoi with an empty strin
• scr: glob ui: fix compiler warnings and msw 32bit project file (thanks Miguel)
• Fix renaming virtual folders with subfolders (ticket #1372).
• SDK: Prevent unexpected renaming of virtual subfolders.

Regressions/Confirmed/Annoying/Common bugs:

[Xaviou]

Hi.

I had an error while building on mac Os :

Code

libtool: compile:  clang++ -std=c++11 -DHAVE_CONFIG_H -I. -I../../../src/sdk -I../../src/include -I/Users/xavier/dev/wx316/build-macOS-11.6/lib/wx/include/osx_cocoa-unicode-3.1 -I/Users/xavier/dev/wx316/include -D_FILE_OFFSET_BITS=64 -DwxDEBUG_LEVEL=0 -DWXUSINGDLL -D__WXMAC__ -D__WXOSX__ -D__WXOSX_COCOA__ -I../../../src/include/scripting/include -I../../../src/include -I../../../src/sdk/wxscintilla/include -I../../../src/sdk/mozilla_chardet/include -I../../../src/sdk/mozilla_chardet/include/mfbt -I../../../src/sdk/mozilla_chardet/include/nsprpub/pr/include -I../../../src/sdk/mozilla_chardet/include/xpcom -I../../../src/sdk/mozilla_chardet/include/xpcom/base -I../../../src/sdk/mozilla_chardet/include/xpcom/glue -DCB_AUTOCONF -DPIC -I../../../src/include/tinyxml -DTIXML_USE_STL=YES -mmacosx-version-min=11.6 -fPIC -fexceptions -MT projectloader_hooks.lo -MD -MP -MF .deps/projectloader_hooks.Tpo -c ../../../src/sdk/projectloader_hooks.cpp  -fno-common -DPIC -o .libs/projectloader_hooks.o
../../../src/sdk/projectloader.cpp:1302:119: error: cannot pass object of non-trivial type 'wxString' through variadic
      function; call will abort at runtime [-Wnon-pod-varargs]
  ...not find project glob with id %s for file %s"), id, file->GetBaseName().wx_str()));
                                                     ^

Regards
Xav'

[MaxGaspa]

Hi,

Uing this latest nigthly (but the issue was present in previous nigthly too) I observed the followin issue:

1) I create a new compiler setup (UCRT64) simply copying the MINGW64 and changin the paths
2) I selected the new UCRT64 as default
3) I restarted CB
4) now the clangd pluging is disabled. I re-enabled the clangd pluging and restared CB
5) Now the clangd plugin is not available even if the plugin is enabled

May be this is a bug. I don't know whether the clangd is expected to work with "official" compiler setups only, in case please add UCRT64 because Msys2 is now considering ucrt variant as the default environment.

Hope this helps

[Miguel Gimenez]

For the compilation error, the line

Code

    Manager::Get()->GetLogManager()->DebugLog(F(_T("Could not find project glob with id %s for file %s"), id, file->GetBaseName().wx_str()));

should be

Code

    Manager::Get()->GetLogManager()->DebugLog(F(_T("Could not find project glob with id %s for file %s"), id.wx_str(), file->GetBaseName().wx_str()));

or better

Code

    Manager::Get()->GetLogManager()->DebugLog(wxString::Format("Could not find project glob with id %s for file %s", id, file->GetBaseName()));

[BlueHazzard]

Fixed in trunk, thank you!

[killerbot]

there is an unwanted change to the cbp file, when using the glob feature, I think there are 2 things wrong:
* it should not be enumerating al the files, the goal is to keep the cbp stable and it picks up all the files within the specified glob directories, the cbp file is also in version control systems, one does not want this to change, this is totally the opposite of the goal of the feature when I added this
* next to this it seems to have bugs with those IDs as you can see below (but since this must disappear wrt the first remark, it will be solved by design :-) )

Code

-               <UnitsGlob directory="../export/" recursive="1" wildcard="" />
-               <UnitsGlob directory="../local/" recursive="1" wildcard="" />
+               <UnitsGlob directory="../export/" wildcard="" recursive="1" id="769713912" />
+               <UnitsGlob directory="../local/" wildcard="" recursive="1" id="3282429397" />
+               <Unit filename="../export/RepeatingTask/RepeatingTaskFactory.h">
+                       <Option glob="769713912" />
+               </Unit>
+               <Unit filename="../export/RepeatingTask/RepeatingTaskIf.h">
+                       <Option glob="769713912" />
+               </Unit>
+               <Unit filename="../local/RepeatingTask.cpp">
+                       <Option glob="-1012537899" />
+               </Unit>
+               <Unit filename="../local/RepeatingTask.h">
+                       <Option glob="-1012537899" />
+               </Unit>
+               <Unit filename="../local/RepeatingTaskFactory.cpp">
+                       <O

the 2 ids handed out to the to directories : the oned used for export is reused for files underneath that directory, but the one for local is not used, instead those files end up with a negative ID.

But as said, there should be no enumeration of files in the cbp in this case, and those IDs and I also not sure if this is a wanted feature...

If for some reason as a role of caching this list would be needed, then I would suggest to put it in the layout file, or create an extra similar 'temporary' file.


EDIT : even a third problem is present, when opening the cbp file again, just rebuild everything, again it said the cbp file was changed (while it had it nicely saved the previous time it told me this).

[BlueHazzard]

My point of view is, that the project file is like a make file. You have to modify a makefile if you add source files to be able to build it.
If you do not add them to the project we have some problems:
1) you can not modify properties of them: Only build with certain build targets ecc.
2) I had other problems with the old implementation, i can not remember any more exactly (it is a 3 years), i think code completion did not work correctly...

We have discussed this with the problems of the original implementation here: http://forums.codeblocks.org/index.php/topic,22783.msg154862/topicseen.html

My opinion on this: This feature was never/seldom used by user before, because it had no ui/documentation. So the risk of breaking some project files is minimal. I also pointed this out in the announcement post (https://forums.codeblocks.org/index.php/topic,25276.0.html). Now it has UI and documentation and we can expect it to be used... I for example need it for an upcoming plugin i currently am working on...
If you are absolutely against this implementation i can try to look into it and add some flag for old and new behaviour?

I will look into the problems with the ids. Thank you for testing and pointing it out.

[Xaviou]

Hi

Fixed in trunk, thank you!

Rev 13209 build fine : thank you

Regards
Xav'

[killerbot]

My point of view is, that the project file is like a make file. You have to modify a makefile if you add source files to be able to build it.
If you do not add them to the project we have some problems:
1) you can not modify properties of them: Only build with certain build targets ecc.
2) I had other problems with the old implementation, i can not remember any more exactly (it is a 3 years), i think code completion did not work correctly...

We have discussed this with the problems of the original implementation here: http://forums.codeblocks.org/index.php/topic,22783.msg154862/topicseen.html

My opinion on this: This feature was never/seldom used by user before, because it had no ui/documentation. So the risk of breaking some project files is minimal. I also pointed this out in the announcement post (https://forums.codeblocks.org/index.php/topic,25276.0.html). Now it has UI and documentation and we can expect it to be used... I for example need it for an upcoming plugin i currently am working on...
If you are absolutely against this implementation i can try to look into it and add some flag for old and new behavior?

I will look into the problems with the ids. Thank you for testing and pointing it out.

When I created this feature, long time ago, the intention is to mimic the glob feature of cmake. We have been relying on this feature extensively, and indeed it is not documented, since one needs to know how to use it, it has limitations, eg when new file is added, one needs to reload the project  to pick up the new files. Code completion works, but not always, but with the old code completion plug-in it also worked like this, sometimes yes, sometimes no, but I can indeed think with this glob it is a bit worse.


Now that said, the cmake world is also no longer in favor of their glob feature (it also has some problems), and want sources to be explicitly added. Which we could translate to CB as :

• we also don't want this feature
• we remove both new and old behavior
• we keep the old behavior as is for backwards compatibility

I do think we need to keep the old behavior for backwards compatibility, since it was there to mimic cmake glob (and then you also did not have to touch the CMakeLists.txt anymore), this needs to be re-instated, because overhere everything is now collapsing.

So please provide the old way, and when the new way is wanted, have CB add per directory an extra flag to say new behavior (old behavior should need no changes to be made by the user), absence of this flag means old behavior.

[killerbot]

I will copy this post in the other thread, so we can continue talking about it there.

[MaxGaspa]

Dear All,

Am I wrong or now it is impossible to remove a source (or header) file from a Project. The right-click menu is no longer offering the menu item to remove a file.

I see the "Remove Files" in the Project menu but deleting multiple files (I selected several files but the removing dialog is offering the possibility to remove the first file in the selection only) is very
uncomfortable....just a right click on the filename was more comfortable.

Thx

[Miguel Gimenez]

Looks like this code from [r13191] (Add UI for automatic source folders aka project globs) prevents it from appearing:

Code

            if (pf->IsGlobValid())
            {
                menu.AppendSeparator();
                menu.Append(idMenuRemoveFilePopup, _("Remove file from project"));
                menu.Enable(idMenuRemoveFilePopup, PopUpMenuOption);
            }

[Pecan]

Dear All,

Am I wrong or now it is impossible to remove a source (or header) file from a Project. The right-click menu is no longer offering the menu item to remove a file.

I see the "Remove Files" in the Project menu but deleting multiple files (I selected several files but the removing dialog is offering the possibility to remove the first file in the selection only) is very
uncomfortable....just a right click on the filename was more comfortable.

Thx

I also experienced this. But with add files. It only added the first file.

[MaxGaspa]

]
I also experienced this. But with add files. It only added the first file.

Pecan, have you read my previous message related to clangd plugin? Is it a real bug?

[BlueHazzard]

Am I wrong or now it is impossible to remove a source (or header) file from a Project. The right-click menu is no longer offering the menu item to remove a file.

fixed in trunk

Looks like this code from [r13191] (Add UI for automatic source folders aka project globs) prevents it from appearing:

yes.. there should be a '!' infront fixed in trunk...

I also experienced this. But with add files. It only added the first file.

i can not reproduce it. Can you give more details?

[Pecan]

Hi,

Uing this latest nigthly (but the issue was present in previous nigthly too) I observed the followin issue:

1) I create a new compiler setup (UCRT64) simply copying the MINGW64 and changin the paths
2) I selected the new UCRT64 as default
3) I restarted CB
4) now the clangd pluging is disabled. I re-enabled the clangd pluging and restared CB
5) Now the clangd plugin is not available even if the plugin is enabled

May be this is a bug. I don't know whether the clangd is expected to work with "official" compiler setups only, in case please add UCRT64 because Msys2 is now considering ucrt variant as the default environment.

Hope this helps

Sorry, I'm lost here.
What are the steps to make UCRT64 a compiler.
I suspect clangd_client is not finding a master path for this compiler you setup and disables itself.
Tell me how to test this step-by-step.  (Im' a bit slow now-a-days).

Sorry I missed this earlier. It's tax season, so my focus is elsewhere lately.

[stahta01]

To MaxGaspa and Pecan:

My guess is clangd executable is not set to a valid value.

Edit: After I installed mingw-w64-ucrt-x86_64-clang-tools-extra I was able to set clangd executable to a valid value.

I did not try testing the plugin I just enable and configured the plugin.

Tim S.

[Pecan]

To MaxGaspa and Pecan:

My guess is clangd executable is not set to a valid value.

Edit: After I installed mingw-w64-ucrt-x86_64-clang-tools-extra I was able to set clangd executable to a valid value.

I did not try testing the plugin I just enable and configured the plugin.

Tim S.

@stahta01
Is this an msys2 install?
What's the commands to do the install you're suggesting.
TIA

[stahta01]

The standard MSys2 command.

Code

pacman -S --needed mingw-w64-ucrt-x86_64-clang-tools-extra

Note: I do not normally use CB these days; but, I use MSys2 on a daily basis.

Tim S.

[MaxGaspa]

What are the steps to make UCRT64 a compiler.
I suspect clangd_client is not finding a master path for this compiler you setup and disables itself.

1) Start with the default MINGW64 compiler setup (working clangd plugin)
2) In Setting->Compiler Copy the MINGW64 and call it UCRT64
3) In Global Complier Setting -> Toolchain executable set the Compiler's installation directory:  Set the new directory (MSYS is using c:\msys64\ucrt64 ) All the program .exe are still valid
4) Click Set as default
5) in the Setting->Configure Editor -> Clangd client -> C/C++ parser -> Specify clangd executable to use I have C:\msys64\ucrt64\bin\clangd.exe (the autodetect is not complaining)
6) close CB and reopen it. No error message or warning is shown.

Now clangd is disabled and it is not possible to re-enable it. If you  re-enable clangd using Plugin->Manage Plugins the " View->Toolbar->clangd_client" is absent

At the moment I'm still using MINGW64 as the defalut compiler and I'm changng the compiler to UCRT64 in my projects using Project->build options-select compiler and everything works well.

In all my testing the clangd executable is correctly set. I installed the mingw-w64-ucrt-x86_64-clang-tools-extra package using pacman (latest version). Please note: the old Mingw64 installation was deleted, now I'm using ucrt64 only.

My guess is clangd executable is not set to a valid value.

The clangd executable was always set to a valid one. The autodetect is not complaining and no warning is present opening CB.


Hope this helps

[Neo]

Just curious, where can I download the latest clangd plugin? The sf.net (https://sourceforge.net/projects/cb-clangd-client/files/Plugin_Install_Package/Windows_x64/) build stays at Oct last year.

[Pecan]

Just curious, where can I download the latest clangd plugin? The sf.net (https://sourceforge.net/projects/cb-clangd-client/files/Plugin_Install_Package/Windows_x64/) build stays at Oct last year.

Clangd_client plugin has already been added to the CodeBlocks build system as a contrib plugin.
It's included in each "Nightly Build" which can be downloaded via this forum. See https://forums.codeblocks.org/index.php/board,20.0.html
(namely the first post in this forum thread).

Clangd_client plugin needs a clangd server process to load. Directions for providing clangd (linux) or clangd.exe(windows) is in the CodeBlocks wiki at https://wiki.codeblocks.org/index.php/CB_Clangd_Client

You can ignore the info in the wiki about building the plugin.
It's already included in the Nightly builds.

[Neo]

Thanks for the direction.

I have a small problem with clangd. The tooltip most of time is too narrow, see the attached picture.

Just curious, where can I download the latest clangd plugin? The sf.net (https://sourceforge.net/projects/cb-clangd-client/files/Plugin_Install_Package/Windows_x64/) build stays at Oct last year.

Clangd_client plugin has already been added to the CodeBlocks build system as a contrib plugin.
It's included in each "Nightly Build" which can be downloaded via this forum. See https://forums.codeblocks.org/index.php/board,20.0.html
(namely the first post in this forum thread).

Clangd_client plugin needs a clangd server process to load. Directions for providing clangd (linux) or clangd.exe(windows) is in the CodeBlocks wiki at https://wiki.codeblocks.org/index.php/CB_Clangd_Client

You can ignore the info in the wiki about building the plugin.
It's already included in the Nightly builds.

[Pecan]

Thanks for the direction.

I have a small problem with clangd. The tooltip most of time is too narrow, see the attached picture.

Just curious, where can I download the latest clangd plugin? The sf.net (https://sourceforge.net/projects/cb-clangd-client/files/Plugin_Install_Package/Windows_x64/) build stays at Oct last year.

Clangd_client plugin has already been added to the CodeBlocks build system as a contrib plugin.
It's included in each "Nightly Build" which can be downloaded via this forum. See https://forums.codeblocks.org/index.php/board,20.0.html
(namely the first post in this forum thread).

Clangd_client plugin needs a clangd server process to load. Directions for providing clangd (linux) or clangd.exe(windows) is in the CodeBlocks wiki at https://wiki.codeblocks.org/index.php/CB_Clangd_Client

You can ignore the info in the wiki about building the plugin.
It's already included in the Nightly builds.

Thanks for the report.
What OS are you running on?

The plugin has no control of the width of the tooltip. It's caused by the core plugin manager.
I'll put it on the "ToDo" list of problems to investigate.
But I won't be able to attend to it until after April (tax season is hear).

[Neo]

Thanks for the direction.

I have a small problem with clangd. The tooltip most of time is too narrow, see the attached picture.

Just curious, where can I download the latest clangd plugin? The sf.net (https://sourceforge.net/projects/cb-clangd-client/files/Plugin_Install_Package/Windows_x64/) build stays at Oct last year.

Clangd_client plugin has already been added to the CodeBlocks build system as a contrib plugin.
It's included in each "Nightly Build" which can be downloaded via this forum. See https://forums.codeblocks.org/index.php/board,20.0.html
(namely the first post in this forum thread).

Clangd_client plugin needs a clangd server process to load. Directions for providing clangd (linux) or clangd.exe(windows) is in the CodeBlocks wiki at https://wiki.codeblocks.org/index.php/CB_Clangd_Client

You can ignore the info in the wiki about building the plugin.
It's already included in the Nightly builds.

Thanks for the report.
What OS are you running on?

The plugin has no control of the width of the tooltip. It's caused by the core plugin manager.
I'll put it on the "ToDo" list of problems to investigate.
But I won't be able to attend to it until after April (tax season is hear).

It's a Windows 8.1 Pro VM. I also tried it in a Windows 10 VM, got same behaviour.

EDIT:
I found the cause of this problem. My system font scaling is set to 125%. I revert it back to 100% and the tooltip window works fine.