User forums > General (but related to Code::Blocks)

Happy New Year

<< < (3/3)

AndrewCot:
@pecan
It appears that processing the files is slow as per the logged info shown below:

Opening D:\Andrew_Development\WorkingOnThese\AC-WindowsInstaller\src\CodeBlocks_wx31_64.cbp
Done.
cbProject::Open took: 0.725 seconds.
ProjectManager::SetProject took: 1.686 seconds.
ProjectManager::LoadProject took: 2.732 seconds.
ParseManager::CreateParser: Finish creating a new parser for project 'Code::Blocks wx3.1.x (64 bit)'
LSP opened editor parse finished for D:\Andrew_Development\WorkingOnThese\AC-WindowsInstaller\src\plugins\clangd_client\src\LSPclient\include\protocol.h (1441 ms) (496 more)
LSP opened editor parse finished for D:\Andrew_Development\WorkingOnThese\AC-WindowsInstaller\src\plugins\clangd_client\src\codecompletion\parser\LSP_tokenizer.h (3194 ms) (495 more)
LSP opened editor parse finished for D:\Andrew_Development\WorkingOnThese\AC-WindowsInstaller\src\plugins\clangd_client\src\codecompletion\codecompletion.cpp (4342 ms) (494 more)
LSP opened editor parse finished for D:\Andrew_Development\WorkingOnThese\AC-WindowsInstaller\src\plugins\clangd_client\src\LSPclient\include\client.cpp (3738 ms) (493 more)
LSP opened editor parse finished for D:\Andrew_Development\WorkingOnThese\AC-WindowsInstaller\src\include\compilerfactory.h (660 ms) (492 more)
LSP opened editor parse finished for D:\Andrew_Development\WorkingOnThese\AC-WindowsInstaller\src\plugins\clangd_client\src\asyncprocess\asyncprocess.cpp (2228 ms) (491 more)
LSP opened editor parse finished for D:\Andrew_Development\WorkingOnThese\AC-WindowsInstaller\src\sdk\configmanager-revision.cpp (3543 ms) (490 more)
LSP opened editor parse finished for D:\Andrew_Development\WorkingOnThese\AC-WindowsInstaller\src\sdk\cygwin.cpp (3534 ms) (489 more)
LSP background parsing finished for: D:\Andrew_Development\WorkingOnThese\AC-WindowsInstaller\src\src\environmentsettingsdlg.cpp (3262 ms) (488 more)

Is there a way of speeding this up? Any ideas on where to look or what to check or do?
I am using MSYS2 with the latest updates as of a few hours ago (this resulted in waht looked like a big MinGW 64 9.00 run time update) and GCC 11.2.0.

Pecan:
@ AndrewCot

I've replied at https://forums.codeblocks.org/index.php/topic,24357.msg169048.html#msg169048

killerbot:
one of the reasons obfuscated was conservative of the c++ standard was, that it could no longer be build on centos. centos typically comes half a decade or more behind of compiler support or whatever other package support (ignoring here the reasons).

Personally I agree with stepping up the compiler standard requirement, we are already on c++20, so we are still conservative ;-)

If this is what it takes to get back in the game for code completion, let's try it out.

killerbot:
well does it also provide code completion , or is it just continuously compiling as you type and telling you already if you have errors ?

Pecan:

--- Quote from: killerbot on January 07, 2022, 08:13:53 pm ---well does it also provide code completion , or is it just continuously compiling as you type and telling you already if you have errors ?

--- End quote ---

clangd_client was built to start providing any feature that was provided in the older CodeCompletion within ~3 seconds (or just after clangd returns from indexing the active editor). The active editor is the first file handed to clangd when a project is loaded.

It does not matter if clangd does not complete all the inactive editors. They just chug along being parsed in the background to provide info to the symbols window.

The order files are handed to clangd are:
   1) The active editor
   2) All the other editor
   3) The most recently modified files (not in an editor)
   4) All other unmodified files (not in an editor)

When a file is activated in an editor, it goes to the front of the line.

Works well for me. Is there any problem with this?
If so, it needs to be fixed. I can do that. (I think) :>)

Navigation

[0] Message Index

[*] Previous page