Use Compiler Configuration or Response files instead of command-line parameters #205
Description
BOSS install/update seems to use command-line parameters to pass paths to Delphi compiler, resulting in failures during boss install/update which write in the respective logs:
The specified task executable "dcc" could not be run. The filename or extension is too long
I tried setting LongPathsEnabled to 1 (on a Win10 pro) and reboot, to no avail
So I ended up using a JUNCTION with a really short path for it like C:\tmpBOSS
But as projects use more and more dependencies they may still fail and have to convert to even smaller junction name for it to work
Can see the workarround I use at
- https://github.com/Zoomicon/READCOM_App/blob/master/BOSS_install.bat
- https://github.com/Zoomicon/READCOM_App/blob/master/BOSS_update.bat
The real solution would be to pass so-called "Compiler Configuration Files" or "Response files" to the compiler, explained near the end of:
https://docwiki.embarcadero.com/RADStudio/Athens/en/BCC32.EXE,_the_C%2B%2B_32-bit_Command-L\ine_Compiler
the former can host only options, the latter can host both options and file names. I think the search paths in the options are the really long ones, so a "Compiler Configuration File" should be enough (could store that .cfg file in the same folder as the .bat and .log for each dependency that gets built so that one can examine it - the failure logs would be more readable too that way)