Author Topic: Bug in CB (version tested last nightly : rev12537)  (Read 3657 times)

Offline ThierryD

  • Single posting newcomer
  • *
  • Posts: 3
Bug in CB (version tested last nightly : rev12537)
« on: November 12, 2021, 05:50:46 pm »
Hello,

I use CB since ten years, and i like it.
I think have to find a "bug". ;D
My environment : Windows 10 (old computer !) and Windows 11 (new portable) 64 bits, and many configurations of free compilers C (and C++, if it's possible ...).
All these configurations of compilers are described in the document in attachement (in french).
One paradigm : only one source(s) to these compilers (one target for each compiler/environment, and one global "virtual target" -> all_build).
After install Visual Studio 2022 community (+ Build Tools 2022) from Microsoft, CB don't recognize neither VS 2022 32 bits, neither VS2022 64 bits. Damn !
And the "discovered" bug is described after :
   in menu "Settings ... Compiler", choose one compiler and position in tab "Search Directories"
   Selection any directory and clic to button "Copy to ...", nothing appear ... !
Another "Damn" for me, because CLANG with VS2022 is again configured within CB after this install.
Thank's for all.
(apologies for my bad english).

Thierry D.


 

Offline Miguel Gimenez

  • Developer
  • Lives here!
  • *****
  • Posts: 929
Re: Bug in CB (version tested last nightly : rev12537)
« Reply #1 on: November 12, 2021, 06:01:21 pm »
IIRC VS2022 does not have a bin folder, so detection and manual setting fail.

Offline ThierryD

  • Single posting newcomer
  • *
  • Posts: 3
Re: Bug in CB (version tested last nightly : rev12537)
« Reply #2 on: November 12, 2021, 06:37:04 pm »
Thank's Miguel.
Yes, I know : \bin don't exist in all version of VS, neither on ..\Hostx86\x86, neither on ..\Hostx64\x64
For this reason, i add these directories in each configuration of VS2022 32 bits and VS2022 64 bits, in "Toolchain executables" on tab "Additional Paths".
The bug of CB is not about this comportement, but affect button "Copy to ..." in "Search Directories" of any compiler defined in CB.
Many thank's for your pertinent response about VS.

Thierry D.

Offline Miguel Gimenez

  • Developer
  • Lives here!
  • *****
  • Posts: 929
Re: Bug in CB (version tested last nightly : rev12537)
« Reply #3 on: November 12, 2021, 06:48:27 pm »
As I understand this issue, the "Copy To" button is used to copy directories between targets when using the
Project -> Build options dialog.

When using Settings -> Compiler the dialog is the same, but IMHO the "Copy To" button has no sense here and it should be disabled or hidden. Same goes for the "Copy selected to" button in Linker settings.

Offline Miguel Gimenez

  • Developer
  • Lives here!
  • *****
  • Posts: 929
Re: Bug in CB (version tested last nightly : rev12537)
« Reply #4 on: November 13, 2021, 11:24:55 am »
The patch in ticket 1154 disables the button when editing the global compiler options.

Offline ThierryD

  • Single posting newcomer
  • *
  • Posts: 3
Re(2) : Bug in CB (version tested last nightly : rev12537)
« Reply #5 on: November 13, 2021, 02:40:38 pm »
Hi Miguel,

Ok, thanks for this complement.
I want just copy all configuration of "Search Directories" between two compilers very similar in "Global compiler options" : CLANG + VS2022 and VS2022 only.
After the installation of VS2022, CB restart and advertise that two configurations aren't found "automatically" (because \bin don't exist ...) : VS2022 32 bits and VS2022 64 bits.
Why patch 1154 disable it ?
For me, this operation should be usually.

Sure, I'm re-configure "manually" all "Search directories" for two configurations VS2022 and CB is operational at new.
Many thanks.

Thierry D.

Offline Miguel Gimenez

  • Developer
  • Lives here!
  • *****
  • Posts: 929
Re: Bug in CB (version tested last nightly : rev12537)
« Reply #6 on: November 13, 2021, 04:55:47 pm »
The button has no use when editing the global compiler settings, in fact the code just returns as you discovered. Disabling it remarks it has no function in this context.

If you want it to copy configurations then you can post a patch, the code fragment in the ticket gives you a starting point.