91
General (but related to Code::Blocks) / Re: Welcome Newcomers - PLEASE READ!!!
« Last post by Code::blocks on April 25, 2025, 01:13:41 pm »I am new, I am here
News:
The new Release 25.03 is out! You can download binaries for Windows and many major Linux distros here .
Recent Posts
92
Using Code::Blocks / Re: ClangD causing cc1plus.exe error pop up dialog on Windows
« Last post by Wkerry on April 25, 2025, 03:57:46 am »More info:
If I change the "GNU GCC Compiler" installation directory from C:\msys64\mingw32 to C:\msys64\mingw64 the error goes away.
I have the "GNU GCC MSYS MinGW64 Compiler" compiler setup as default.
The CC_ProxyProject.cbp has the <Option compiler="gcc" /> which when I load it and look at which compiler it is using it is the "GNU GCC Compiler" compiler. It looks like "GNU GCC Compiler" has at some stage has detected the compiler in the C:\msys64\mingw32 directory.
I did configure MSYS2 for both 32 and 64 bit originally as I had to support some 32 bit XP apps, but I have not used the 32 bit tool-chain for a few years.
If I change the "GNU GCC Compiler" installation directory from C:\msys64\mingw32 to C:\msys64\mingw64 the error goes away.
I have the "GNU GCC MSYS MinGW64 Compiler" compiler setup as default.
The CC_ProxyProject.cbp has the <Option compiler="gcc" /> which when I load it and look at which compiler it is using it is the "GNU GCC Compiler" compiler. It looks like "GNU GCC Compiler" has at some stage has detected the compiler in the C:\msys64\mingw32 directory.
I did configure MSYS2 for both 32 and 64 bit originally as I had to support some 32 bit XP apps, but I have not used the 32 bit tool-chain for a few years.
93
Development / Re: Custom variables
« Last post by LETARTARE on April 25, 2025, 02:00:56 am »Thank you very much.
This is exactly what I needed to read user-defined variables from a project.
This is exactly what I needed to read user-defined variables from a project.
94
Using Code::Blocks / Re: ClangD causing cc1plus.exe error pop up dialog on Windows
« Last post by stahta01 on April 24, 2025, 07:04:39 pm »Somewhere there is a setting for which clangd is used by Code::Blocks check that is correct.
Edit: Best guess "settings->Editor"
To devs: Feature request that the setting of "$(TARGET_COMPILER_DIR)\bin\clangd.exe" works for clangd plugin; the clang plugin already has the code; but, the value of $(TARGET_COMPILER_DIR) is not know at the point in time; might not be possible for it to be known
Edit2: Looks like code is too complex for me to understand ClgdCompletion::OnAppStartupDone
Tim S.
I'll look to see if this is workable.
I vaguely remember that I tried this, but the needed macros were unknown at project load which is where the clangd.exe needs to be set.
But I'll look at it again anyway.
It does replace with global variable which means you are likely right and the value is empty at that time.
Edit: A more important related bug is it fails to find the clangd.exe in the MINGW installation folder of an CB installed with Mingw compiler.
95
Using Code::Blocks / Re: ClangD causing cc1plus.exe error pop up dialog on Windows
« Last post by Pecan on April 24, 2025, 06:41:28 pm »Somewhere there is a setting for which clangd is used by Code::Blocks check that is correct.
Edit: Best guess "settings->Editor"
To devs: Feature request that the setting of "$(TARGET_COMPILER_DIR)\bin\clangd.exe" works for clangd plugin; the clang plugin already has the code; but, the value of $(TARGET_COMPILER_DIR) is not know at the point in time; might not be possible for it to be known
Edit2: Looks like code is too complex for me to understand ClgdCompletion::OnAppStartupDone
Tim S.
I'll look to see if this is workable.
I vaguely remember that I tried this, but the needed macros were unknown at project load which is where the clangd.exe needs to be set.
But I'll look at it again anyway.
96
Using Code::Blocks / Re: ClangD causing cc1plus.exe error pop up dialog on Windows
« Last post by stahta01 on April 24, 2025, 05:47:43 pm »Possible work around what I am guessing is the cause.
A. Add Global var of "MSYS2_MINGW64" set base to "C:\msys64\mingw64"
1. Settings -> global variables
2. Add Global var of "MSYS2_MINGW64"
3. Set base to correct location ex. "C:\msys64\mingw64"
B. Set path of clang exec to use to "$(#MSYS2_MINGW64)\bin\clangd.exe"
1. Settings -> Editor
2. Select clangd_client from left pane
3. Tab "C/C++ parser"
4. Set exec to use to "$(#MSYS2_MINGW64)\bin\clangd.exe"
Tim S.
A. Add Global var of "MSYS2_MINGW64" set base to "C:\msys64\mingw64"
1. Settings -> global variables
2. Add Global var of "MSYS2_MINGW64"
3. Set base to correct location ex. "C:\msys64\mingw64"
B. Set path of clang exec to use to "$(#MSYS2_MINGW64)\bin\clangd.exe"
1. Settings -> Editor
2. Select clangd_client from left pane
3. Tab "C/C++ parser"
4. Set exec to use to "$(#MSYS2_MINGW64)\bin\clangd.exe"
Tim S.
97
Plugins development / CC NONPCH issue/patch for wxWidgets 3.3
« Last post by stahta01 on April 24, 2025, 05:07:34 pm »Code
Subject: codecompletion: Add include of "wx/xrc/xmlres.h" for nonPCH builds
---
src/plugins/codecompletion/parsemanager.cpp | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/plugins/codecompletion/parsemanager.cpp b/src/plugins/codecompletion/parsemanager.cpp
index 281fb5142..21d3e7b7e 100644
--- a/src/plugins/codecompletion/parsemanager.cpp
+++ b/src/plugins/codecompletion/parsemanager.cpp
@@ -16,6 +16,7 @@
#include <wx/log.h> // for wxSafeShowMessage()
#include <wx/regex.h>
#include <wx/wfstream.h>
+ #include <wx/xrc/xmlres.h>
#include <cbauibook.h>
#include <cbeditor.h>
--
98
General (but related to Code::Blocks) / Re: What can i do?
« Last post by stahta01 on April 24, 2025, 04:52:44 pm »With out more information it is unlikely someone will help you!
1. Code::Blocks version
2. Operating System (OS)
3. OS Version
4. Compiler name
5. Compiler version
6. Programming Language in code with issue C or C++
Edit: Even with that information; I will not be able to help you; but, with that info someone likely will be able to help you.
Tim S.
1. Code::Blocks version
2. Operating System (OS)
3. OS Version
4. Compiler name
5. Compiler version
6. Programming Language in code with issue C or C++
Edit: Even with that information; I will not be able to help you; but, with that info someone likely will be able to help you.
Tim S.
99
Using Code::Blocks / Re: ClangD causing cc1plus.exe error pop up dialog on Windows
« Last post by stahta01 on April 24, 2025, 03:52:02 pm »Somewhere there is a setting for which clangd is used by Code::Blocks check that is correct.
Edit: Best guess "settings->Editor"
To devs: Feature request that the setting of "$(TARGET_COMPILER_DIR)\bin\clangd.exe" works for clangd plugin; the clang plugin already has the code; but, the value of $(TARGET_COMPILER_DIR) is not know at the point in time; might not be possible for it to be known
Edit2: Looks like code is too complex for me to understand ClgdCompletion::OnAppStartupDone
Tim S.
Edit: Best guess "settings->Editor"
To devs: Feature request that the setting of "$(TARGET_COMPILER_DIR)\bin\clangd.exe" works for clangd plugin; the clang plugin already has the code; but, the value of $(TARGET_COMPILER_DIR) is not know at the point in time; might not be possible for it to be known
Edit2: Looks like code is too complex for me to understand ClgdCompletion::OnAppStartupDone
Tim S.
100
Using Code::Blocks / Re: ClangD causing cc1plus.exe error pop up dialog on Windows
« Last post by gd_on on April 24, 2025, 12:11:16 pm »Your installation look strange. If your rename solves the problem, it's probably because you use something inside mingw32, so you mix 32 and 64 bits exes. Check the paths and their order.
I use also msys2 distribution, also with clangd which is inside c:\msys64\mingw64\bin (as installed by mingw-w64-x86_64-clang-tools-extra msys2 package). As I use only 64 bits, all folders like C:\msys64\mingw32, C:\msys64\clang32 or C:\msys64\clang64 contain only empty folders, so for me, no way to use something there.
I use also msys2 distribution, also with clangd which is inside c:\msys64\mingw64\bin (as installed by mingw-w64-x86_64-clang-tools-extra msys2 package). As I use only 64 bits, all folders like C:\msys64\mingw32, C:\msys64\clang32 or C:\msys64\clang64 contain only empty folders, so for me, no way to use something there.