Revisit of internal comands used by CB to build on Win32 and proposals evolution

[ThierryD]

Hi Team CB
Hi Tim, Hi Miguel and others developers.

In join memo, you can find "my" revisit of internal comands used by CB to build targets on Win32 systems with several configurations of free compilers C/C++.
I add into it, proposals to make the internal commands much adapted with recent versions of these compilers or much adequate, and repair some syntax errors.

I think it's preferable to read in full text join (sorry long text because many explanations) to understand big principles of my reflection.

I also propose to improve automatic detection of these compilers at startup of CB by indicate the "last" directory present on WIN11 to be sure to find an compiler under theses (if you conserve "default" directory during installation). 
 
To simplify reading, in this text, I frame all my proposals and ask about evolutions of CB by :
-------------------------------------------------------------------------------------------------------------------------------------
.....
-------------------------------------------------------------------------------------------------------------------------------------

I'm just an user of CB, I think also that my asks are reasonable, but you are only judges to accept or not my proposals. 

Thank's for your read, all of my asks are tested and work on my system configurations (W11 24H2 and 23H2 64 bit).

Wait to your returns.

Many thank's.

Thierry.

[Wkerry]

Unordered:
   Executive summary is?
   Executive proposal is?
   Executive problem this is solving is?
   Which of the compilers in a..j are still supported? No

The file is 1862 lines and you expect C::B devs to read and understand the file without explaining your "memo/revist"  notes/ramblings/etc?

There is no C::B proposal as codes changes need to be supplied as patches and I cannot quickly see any patches in the txt file. 

If there are manual changes then these are in separate SVN directory on Sourceforge that patches should be supplied for.
If ther are wiki pages then see if you can update/add pages.

Overall IMHO 2c worth of feedback is that for ANY open source project you would like to contribute to you need to fit in with the way the project works in order to get changes included otherwise your changes will end up in the bit bucket.

[ThierryD]

Hi,

Just to response :
   Executive summary  : Revisit of internal comands used by CB to build on Win32 and proposals evolution
   Executive proposal :   Propose just an evolution of these internals commands to be adapt to compilers C/C++ described into my "simple text" + ameliorate "automatic" detection of these compilers at startup of CB on Win32 systems
   Executive problem this is solving :  Adapt configuration of CB to newest version of these compilers to be a little bit in phase with "modern" but also ancient compilers C/C++, and  ameliorate "automatic" detection of these compilers at startup of CB on Win32 systems
   Which of the compilers in a..j are still supported? No   ->  Ok, and my question -> what is the "habitual" compiler to produce executive version of CB on Win32 systems ?

You have not time to read this text. OK.

My objective is not to propose "patch" to make an evolution of source code of CB, just ask to integrate an evolution of configurations of CB on Win32 and grow list of supported C/C++ compilers (I'm not experiment developer C++, just an "lambda" user of CB that search to ameliorate IDE).

I understand your position od developer, focus on source code only, and sorry if I have not respect your habits of open source project.

Sincerly.

PS : To be curious, I'm have downloaded source code of CB. But big diving into many sources to understand logic and organization of these.