User forums > Nightly builds

The 12 February 2023 build (13205) is out.

<< < (4/5) > >>

Pecan:

--- Quote from: MaxGaspa on February 12, 2023, 10:50:05 am ---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

--- End quote ---

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:

--- Quote from: stahta01 on February 17, 2023, 12:15:43 am ---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.

--- End quote ---

@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

--- End code ---

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

Tim S.

MaxGaspa:

--- Quote from: Pecan on February 16, 2023, 11:22:25 pm ---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.

--- End quote ---

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.



--- Quote from: stahta01 on February 17, 2023, 12:15:43 am ---My guess is clangd executable is not set to a valid value.

--- End quote ---

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

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version