Recent Posts

51

General (but related to Code::Blocks) / Re: Changing fuse settings for Atmega 328P from DEFAULT

« Last post by Miguel Gimenez on April 10, 2024, 06:06:15 pm »

Using Atmel Studio with the ATmega32U4 I just use this in main.c:

Code

FUSES =
  {
  .low = (FUSE_SUT1 & FUSE_CKDIV8),
  .high = (FUSE_BOOTSZ0 & FUSE_BOOTSZ1 & FUSE_EESAVE & FUSE_SPIEN & FUSE_JTAGEN),
  .extended = (FUSE_BODLEVEL2 & FUSE_BODLEVEL1 & FUSE_BODLEVEL0)
  };

The 328 should be similar.

52

Plugins development / Re: Code completion using LSP and clangd

« Last post by Pecan on April 10, 2024, 05:43:01 pm »

Your compiler is just fine where it is.
But for the time being lets use the one in the April 1 nightly so we both are in sync with each other.
You can change it later if you wish.

wait a minute. the zip file of the nightly build(from 1st April) that I downloaded didn't had any compiler in it, just a folder named "shared"

Actually, there is a URL on the Nightly announcement that can be used to download the compiler that was used to make the Nightly CodeBlocks.

But you've solved your setup problems already.
Thanks for your patience and your persistence.
This has informed me on what can go awry and how to improve the instructions on setting up Clangd_client.

You might want to go through the list of plugins (mainmenu/plugins/manage plugins) and disable or uninstall the plugins that you do not use.  It'll unclutter your logs section.

If you haven't found it yet, the "LSP messages" tab in the  log section is the one that contains the output from Clangd/Clangd_client  and may have suggestions on how to correct syntax or symbol references.
If you see a message that contains "(fix available)" you can right-mouseClick on the message and apply the fix automatically if you agree with the suggested fix.

In the coming Nightly, you will also be able to Alt-LeftMouseClick on the red/green warning/error box in the margin to apply any suggested fix.
But you might have to update to mingw64/clangd.exe version 18 (when it becomes available in msys64) before you can take full advantage of this.

Regards

53

General (but related to Code::Blocks) / Having ISSUES with running console apps on Windows 11. Help!

« Last post by Frank Scrooby on April 10, 2024, 05:25:09 pm »

Hi all,

Please forgive me if this message is posted to the wrong forum, or if it has been asked before.

My searching of this site turned up nothing concerning Windows 11, console apps, and CodeBlocks 20.03

I'm doing tiny, little, console apps for an EDX course I want to complete. Like really, really small, nothing bigger than a couple of functions, no big numbers or huge files or anything big.

Code compiles with no complaints.

When I run the program the Windows console pops up but my program does not appear sometimes for seconds but increasingly its more like minutes. One app (about 16 calculations) tooks 3 seconds to run one time and 720 seconds to run the next time.

When I browse into the debug folder and try to run the app from there I get mostly similiar results. Or worse, Windows tells me it doesn't trust my program.

Obviously the solution to my problem would be a nice, neat, compact Linux Distro that is familliar with a newish notebook that has AMD chips. But its not my computer so I can't go changing things like that.

Any help, advice?

If I am being fantastically stupid, please let me know.

regards
Frank Scrooby

54

General (but related to Code::Blocks) / Changing fuse settings for Atmega 328P from DEFAULT

« Last post by mikejp56 on April 10, 2024, 04:55:42 pm »

Hi All,
I am pretty new to CodeBlocks and Atmega 328P programming.
I have a simple code that blinks and LED and uses the default fuse settings for the 3 fuses in fuse.c. I would like to change the lfuse setting from 0x62 to 0xFF so I can use a crystal. How would I change ".low=LFUSE_DEFAULT" to use 0xFF? I have tried multiple things; .low=0xFF, etc. and I keep getting errors for the setting. I can change the lfuse setting in AVRDUDESS and AVRDude and the crystal setting works. I just cannot figure out the syntax for CodeBlocks.
By the way this is an awesome program for a non-programmer to learn on!
Thanks and regards.
mikejp56

55

Plugins development / Re: Code completion using LSP and clangd

« Last post by kakas on April 10, 2024, 10:24:19 am »

SOLVEDDD

I had to set the default compiler to *No-compiler*
before enabling or disabling any plugin.

this time(having no-compiler as default) it didn't gave the error pop-up on the bottom right when enabling the Clangd_Client plugin, but said CB needs to restart for the plugin to function properly.

After setting up the clangd.exe path in the editor settings and restarting again, the plugin works. And it's awesome 

56

Plugins development / Re: Code completion using LSP and clangd

« Last post by kakas on April 10, 2024, 09:40:46 am »

Your compiler is just fine where it is.
But for the time being lets use the one in the April 1 nightly so we both are in sync with each other.
You can change it later if you wish.

wait a minute. the zip file of the nightly build(from 1st April) that I downloaded didn't had any compiler in it, just a folder named "shared"

57

Plugins development / Re: Code completion using LSP and clangd

« Last post by kakas on April 10, 2024, 09:28:47 am »

ran the other command from the guide "pacman -S mingw-w64-x86_64-clang-tools-extra" which downloaded the executables to mingw64 folder instead of clang64.
sorry I got mixed up by the commands in the guide at first (attached screenshot of command prompt showing version details of clangd.exe and c++.exe)

Went through the enabling plugin procedure again to see if it fixed the issue. But no pogress.

Despite the "To run Clangd_Client, restart CodeBlocks after setting up a compiler...." error,
Code blocks seems to compile files just fine. Compiler installation directory(contains clangd.exe and clang.exe) C:\msys64\mingw64.
So I am not sure if the problem comes from CB not finding a default compiler.

58

Plugins development / Re: Code completion using LSP and clangd

« Last post by kakas on April 10, 2024, 08:11:43 am »

Important:
You have to use the clangd.exe under the mingw64 folder. Not the clang64 folder.
Using the wrong clangd.exe is what was causing all the diagnostic errors.

oh I think this is causing the problem. I have no clangd.exe or clang.exe in my mingw64 folder. It's only present in clang64 folder.
Is there another command that I should be running from the msys terminal to download the correct clangd.exe? because I remember running only a single command from the guide.

59

Plugins development / Re: Code completion using LSP and clangd

« Last post by Pecan on April 10, 2024, 07:26:23 am »

hmm. I haven't actually moved the compiler inside the code blocks folder(the one that I made for nightly build). will it have any effect?
(my compile is in, C:\msys64\mingw64\bin)

I Installed the April 1st build.
I disabled "Code_Completion" and than enabled "Clangd_Client".
closed Code Blocks. restarted it again.
open up plugin manager.
And see "Clangd_Client" is disabled.
Basically no difference

Your compiler is just fine where it is.
But for the time being lets use the one in the April 1 nightly so we both are in sync with each other.
You can change it later if you wish.

The Clangd_client is not enabling itself because CB did not find a default compiler. Go to mainMenu/Setting/Compiler/Toolchain executable and set the compiler location as show in the second image below but using your compiler location of course.

Restart CB and you'll see that Clangd_client is now enabled.

Go to mainMenu/Settings/Editor/Clangd_client/C/C++ parser (the second tab) and  put the location of your ...\msys64\mingw64\bin\clangd.exe into the "specify clangd executable to use" search slot. Click ok at bottom.
See the first image below.
Close and restart CB.


Important:
You have to use the clangd.exe under the mingw64 folder. Not the clang64 folder.
Using the wrong clangd.exe is what was causing all the diagnostic errors.

Now do us a favor. Open a cmd window and cd to the folder that contains your ...\msys64\mingw64\bin\clangd.exe and type: (without the quotes)
"clangd.exe --version" and tell us what it printed.
Also type: "c++.exe --version" and tell us what it printed.

Regards

60

Plugins development / Re: Code completion using LSP and clangd

« Last post by kakas on April 09, 2024, 09:14:46 pm »

hmm. I haven't actually moved the compiler inside the code blocks folder(the one that I made for nightly build). will it have any effect?
(my compile is in, C:\msys64\mingw64\bin)

I Installed the April 1st build.
I disabled "Code_Completion" and than enabled "Clangd_Client".
closed Code Blocks. restarted it again.
open up plugin manager.
And see "Clangd_Client" is disabled.
Basically no difference