Author Topic: The 13 August 2022 build (12864) is out.  (Read 8504 times)

Offline gd_on

  • Lives here!
  • ****
  • Posts: 732
Re: The 13 August 2022 build (12864) is out.
« Reply #30 on: August 17, 2022, 06:55:26 pm »
Here is a new reworked version of my windows cbps : call to update.bat are now wxwidgets version independant, except for the main one, at the root.
good tests !
« Last Edit: August 25, 2022, 07:18:21 pm by gd_on »
Windows 10 64 bits (21H2), svn C::B (last version or almost!), wxWidgets 3.2.1, Msys2 Compilers 12.2.0, 64 bits (seh, posix : gcc, g++ and gfortran in C:\msys64\mingw64) or 32 bits (dwarf2, posix  in C:\msys64\mingw32).

Offline Pecan

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 2448
Re: The 13 August 2022 build (12864) is out.
« Reply #31 on: August 18, 2022, 10:56:07 pm »
The Clangd_Client for this nightly can be downloaded at
https://sourceforge.net/projects/cb-clangd-client/files/Plugin_Install_Package/Windows_x64/

Filename: ClangdClientForCBNightly_20220813_rev12864_win64.zip (Direct download link)

Copy the included clangd_client.zip to  <YourCodeBlocksNightlyFolder>\share\CodeBlocks\clangd_client.zip
Do not unzip this file.

Copy the included clangd_client.dll to <YourCodeBlocksNightlyFolder>\share\CodeBlocks\plugins\clangd_client.dll

Restart your CodeBlocks Nightly.

Install instructions for LLVM/clangd are included within the downloaded .zip file.
Modify message

Offline AndrewCot

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 652
Re: The 13 August 2022 build (12864) is out.
« Reply #32 on: August 19, 2022, 11:46:45 am »
@gd_onI finally got a little time to check out your project files and the 10 or so I looked at were great. I will take a break from the stuff I have been working on and take the time to update my files with the changes.

Offline gd_on

  • Lives here!
  • ****
  • Posts: 732
Re: The 13 August 2022 build (12864) is out.
« Reply #33 on: August 19, 2022, 12:49:30 pm »
Thanks for testing.
A small tip : the base field of cb_build is not used here. You can simply put "" in this field. You can also put the path of src of Code::Blocks sources, which could be useful if you use the full paths to the sources in the cbps. But, as I use only relative path, it's not used.
gd_on
Windows 10 64 bits (21H2), svn C::B (last version or almost!), wxWidgets 3.2.1, Msys2 Compilers 12.2.0, 64 bits (seh, posix : gcc, g++ and gfortran in C:\msys64\mingw64) or 32 bits (dwarf2, posix  in C:\msys64\mingw32).

Offline MaxGaspa

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: The 13 August 2022 build (12864) is out.
« Reply #34 on: August 19, 2022, 03:50:35 pm »
@Pecan

I installed the new version of your plugin using the latest nightly (Windows 7 pro SP1). I also installed the package

mingw-w64-x86_64-clang-tools-extra

in my MinGW64 installation and the related required dependencies (automatically installed  using pacman -S )

At the moment I have the version 14.0.6

Massimo@user-PC MINGW64 ~
$ clang -v
clang version 14.0.6
Target: x86_64-w64-windows-gnu
Thread model: posix
InstalledDir: C:/msys64/mingw64/bin

Massimo@user-PC MINGW64 ~
$ clangd -version
clangd version 14.0.6
Features: windows
Platform: x86_64-w64-windows-gnu

Massimo@user-PC MINGW64 ~
$

I configured the pluging and the clangd path was detected automatically. Now using any project I have (including the simplest one created with template "console application" I'm continuosly getting  two message windows attached.

The symbol browser is empty and the Codeblocks log  is

Opening C:\Development\Projects\aaaa\aaaa.cbp
Done.
ParseManager::CreateParser: Finish creating a new parser for project 'aaaa'
ProjectManager::SetProject took: 0.161 seconds.
ProjectManager::LoadProject took: 0.167 seconds.
LSP background parsing FINISHED for: (aaaa) C:\Development\Projects\aaaa\main.cpp (550 ms) (0 more)

I'm also attaching the simple project aaaa in the next  message

Is there any action I can do for helping?

Regards

Max










Offline MaxGaspa

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: The 13 August 2022 build (12864) is out.
« Reply #35 on: August 19, 2022, 03:51:32 pm »
@pecan

Just attaching the aaaa project

Max

Offline MaxGaspa

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: The 13 August 2022 build (12864) is out.
« Reply #36 on: August 19, 2022, 08:35:42 pm »
@pecan

I think I fixed the issue I had with your plugin. I discovered that I had a disk issue saving to the temporary folders. After a scandisk and deleting (forcing) the temp directory and using a new one the observed issue disappeared.  So it seems that the errors saving in the temp directory caused the issue.

Now your plugin is working (well !) and also the crashes i had in the past with a previous version are disappeared.

Max

Offline Pecan

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 2448
Re: The 13 August 2022 build (12864) is out.
« Reply #37 on: August 19, 2022, 08:58:06 pm »
@pecan

Just attaching the aaaa project

Max

Your aaaa project work perfectly on the latest CB nightly, here on my wx3.1.7 installation.

I suspect that the auto detect of clangd.exe is incorrect.
From the base of your msys64 install, using a command windows, issue the command "dir /s clangd*"

You'll probably find that you have two clangd.exe modules.
Like:
Code
F:\user\programs\msys64_13.0.1>dir /s clangd*
 Volume in drive F is HPHD2
 Volume Serial Number is 0873-0556

 Directory of F:\user\programs\msys64_13.0.1\clang64\bin

02/04/2022  11:50 AM        14,887,424 clangd.exe
               1 File(s)     14,887,424 bytes

 Directory of F:\user\programs\msys64_13.0.1\mingw64\bin

02/04/2022  11:49 AM        12,204,466 clangd.exe
               1 File(s)     12,204,466 bytes

Note that there's one clangd.exe in mingw64\bin
and another in clang64\bin.

Look into Setting/Editor/Clangd_client/ tab C/C++ Parser at the entry "Specify Clangd executable to use" and make sure it's set to your directory of mingw64/bin/clangd.exe

« Last Edit: August 19, 2022, 09:00:04 pm by Pecan »

Offline MaxGaspa

  • Multiple posting newcomer
  • *
  • Posts: 12
Re: The 13 August 2022 build (12864) is out.
« Reply #38 on: August 19, 2022, 09:33:57 pm »

Your aaaa project work perfectly on the latest CB nightly, here on my wx3.1.7 installation.

I suspect that the auto detect of clangd.exe is incorrect.
From the base of your msys64 install, using a command windows, issue the command "dir /s clangd*"

You'll probably find that you have two clangd.exe modules.

I have just one clangd.exe in mingw64 but, as I reported the issue was related to some problems writing to the temp directory. I apologize for the time waste but I discovered the disk issue after  posting the messages (and I discovered it because another application was complaining...)

Now I'd like to know if I have discovered a bug or a feature.

Using a large project it is useful to reduce the symbol browser to show the current file symbols only. But switching from "Current Project's symbols" to "Current file's symbols" no changes in the symbol browser happens. See images. Moreover the namespace is not expanded regardless the setting "Automatically expand namespaces".

Great work anyway !!!!

 

Offline Pecan

  • Plugin developer
  • Lives here!
  • ****
  • Posts: 2448
Re: The 13 August 2022 build (12864) is out.
« Reply #39 on: August 20, 2022, 07:04:28 pm »
Partial quote
Now I'd like to know if I have discovered a bug or a feature.

Using a large project it is useful to reduce the symbol browser to show the current file symbols only. But switching from "Current Project's symbols" to "Current file's symbols" no changes in the symbol browser happens. See images. Moreover the namespace is not expanded regardless the setting "Automatically expand namespaces".

@MaxGaspa, thanks for testing and thanks for the input.

Unfortunately I've not had the time to pay much attention to the Symbol browser. I hope to do so some time in the future when clangd_client core code runs sucessfully for one month without need of serious fixing.

I've entered the missing features (as you've noted) into the clang_client ticket system so they won't get lost.

Does it help to view/expand the namespace name instead (see attatched image) ?
« Last Edit: August 20, 2022, 07:25:57 pm by Pecan »

Offline Frank_CB

  • Multiple posting newcomer
  • *
  • Posts: 115
Re: The 13 August 2022 build (12864) is out.
« Reply #40 on: August 20, 2022, 09:55:16 pm »
@gd_on:
If I read what you downloaded correctly, you have it setup for a 32-bit build using a particular 32-bit compiler.  Have you given any thought to being able to use any 32-bit/64-bit compiler?

Regards

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7298
    • My Best Post
Re: The 13 August 2022 build (12864) is out.
« Reply #41 on: August 21, 2022, 08:27:17 am »
@gd_on:
If I read what you downloaded correctly, you have it setup for a 32-bit build using a particular 32-bit compiler.  Have you given any thought to being able to use any 32-bit/64-bit compiler?

Regards

Do you have any reason to believe what you posted?
The only 32 I found was for wxWidgets 3.2 the stuff I found used 64 for osbits.

So, what are you talking about if it is not "Cbps_3.7z" in https://forums.codeblocks.org/index.php/topic,25068.msg170872.html#msg170872 ?

Tim S.
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Stretch, compiling CB Trunk against wxWidgets 3.0.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline gd_on

  • Lives here!
  • ****
  • Posts: 732
Re: The 13 August 2022 build (12864) is out.
« Reply #42 on: August 21, 2022, 10:01:26 am »
my cbp are not so different than standard ones. This work, based on Andrew Cotrell's one, try to avoid some hard coding settings.
Main differences are in folder name build which are initialised with global variables instead of beeing hard coded.
May be the major diference for 32 bit build is : for example with wxWidgets 3.1, the forder name with standard build are .objs31 and devel31, and with my cbp they are .objs31_32 and devel31_32, following the same logic than for 64 build names.
Also, compilation option -m32 or -m64 is built according to the global variable cb_build.osbits. The same for the name of the used wxwidgets libraries.
The compiler is simply gcc (as in standard build). So it's the 1st compiler found in your system path : it may be 32 or 64 bits, depending of your path settings order.
« Last Edit: August 21, 2022, 10:25:31 am by gd_on »
Windows 10 64 bits (21H2), svn C::B (last version or almost!), wxWidgets 3.2.1, Msys2 Compilers 12.2.0, 64 bits (seh, posix : gcc, g++ and gfortran in C:\msys64\mingw64) or 32 bits (dwarf2, posix  in C:\msys64\mingw32).

Offline Frank_CB

  • Multiple posting newcomer
  • *
  • Posts: 115
Re: The 13 August 2022 build (12864) is out.
« Reply #43 on: August 21, 2022, 09:26:58 pm »
@gd_on:
Currently building a 64-bit version of SVN 12877, using re-named and  up-dated versions of Codeblocks_wx31_64.cbp and ContribPlugins_wx31_64.workspace. The plugins' cbp and update*.bat (if provided) files were also re-named and up-dated.

However, prior to using my cbp and workspace files, I placed the files you provided in cbps_3.7z into the proper directories and updating my global variables. Attempting to use your Codeblocks_Windows.cbp and codenlocks_Windows.workspace resulted in errors preventing the build to start. Couldn't seem to find the compiler.  No changes made to oolchain.

Any idea what's cauings this behavior?

Regards

Offline Frank_CB

  • Multiple posting newcomer
  • *
  • Posts: 115
Re: The 13 August 2022 build (12864) is out.
« Reply #44 on: August 21, 2022, 10:09:36 pm »
@gd_on:
The code at the start of Codeblocks_Windows.cbp and Codeblocks_wx32_64.cbp
Code
?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<CodeBlocks_project_file>
<FileVersion major="1" minor="6" />
<Project>
<Option title="Code::Blocks Windows" />
<Option default_target="src" />
<Option compiler="gcc" />
<MakeCommands>
<Build command="" />
<CompileFile command="" />
<Clean command="" />
<DistClean command="" />
<AskRebuildNeeded command="" />
<SilentBuild command=" &gt; $(CMD_NULL)" />
</MakeCommands>
<Build>

=======================================================================

?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<CodeBlocks_project_file>
<FileVersion major="1" minor="6" />
<Project>
<Option title="Code::Blocks wx3.2.x (64 bit)" />
<Option default_target="src" />
<Option compiler="gnugcc_x64_compiler" />
<Build>


The Make commands in your .cbp Throw me. Are they necessary?

Regards