The .cfg I am using once or twice a year.
My Borland Installation is in folder "D:\GreenApps\BCC61"; this would need to be adjust to match your installation folder.
I have been trying bcc32 a few times a year for over a decade; I find setting up the cfg files is faster than configuring all the settings in Code::Blocks. Both methods work.
Note, I am usually doing very simple Borland coding projects.
Tim S.
bcc32.cfg
-I"D:\GreenApps\BCC61\include\";"D:\GreenApps\BCC61\include\vcl\";"D:\GreenApps\BCC61\include\dinkumware\";"D:\GreenApps\BCC61\include\Indy10\"
-L"D:\GreenApps\BCC61\lib\";"D:\GreenApps\BCC61\lib\obj\";"D:\GreenApps\BCC61\lib\release\";"D:\GreenApps\BCC61\lib\PSDK\";"D:\GreenApps\BCC61\lib\Indy10\"
ilink32.cfg
-L"D:\GreenApps\BCC61\lib\";"D:\GreenApps\BCC61\lib\obj\";"D:\GreenApps\BCC61\lib\release\";"D:\GreenApps\BCC61\lib\Indy10\";"D:\GreenApps\BCC61\Lib\PSDK"