User forums > Help
Execution of Compiler Failed
FEA:
Regarding the patch script, does one just use Settings/Scripting/Add/(Select the script)/OK/Allow execution of this command for all scripts from now on ?
For reference, when reading the source code in (recursively) it takes about 10 minutes because there are about 1900 files. After enacting the script, it took about 20 minutes.
I then did a Rebuild and it went along then did something new (so I guess the script was trying to work?). It briefly said said something about "can not read timestamp" in red for many files (it was scrolling) then the CodeBlocks window disappeared/crashed.
So maybe there is no way to resolve this?
FEA:
I was able to get it to compile if I flattened all the source files to a single directory and then renamed all the files to a shorter version. While this works, its not a very practical working solution. This approach reduced the command line to about 19k characters and I believe the limit is 32k characters.
I am not sure why Visual Studio/Intel Fortran has no issues with things as is. From the build log, it seemed to be a single line at the end, so maybe they are rolling it all up into a temporary file before creating the EXE? I wonder if something like that could be done in C::B?
Miguel Gimenez:
This temporary file is called a response file. BlueHazzard is working on adding this to C::B, see https://sourceforge.net/p/codeblocks/tickets/953/.
FEA:
Thanks, I saw that from the prior link. I tried to run the script, but it did not work for me. But now I realized there is a patch file as well. I was confused about how to implement or if it even worked. Some of the commenters were saying that there might be a different approach? But maybe I can just sit tight and wait for this to be implemented.
BlueHazzard:
Will try to make a new patch today, so we can push it in the next days..
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version