I had previously asked a question about a problem I was having with the number of files in a project. At the time I had thought it was just a Simplicity v3.3 problem, and that upgrading to v4 had fixed it. Unfortunately, the problem quickly came back after a few more files were added.
It turns out this is an Eclipse CDT issue, specifically due to the 32K limit on the input of the CreateProcess function. At this time the issue remains unsolved.
The fix I've used is to write all the parameters to a file, and then read those in for the call to the linker. (The link step is where the problem is, as it tries to call gcc with all of the object code in a single command line). In Project->Properties->C/C++ Build->Settings->GNU ARM C Linker, I changed the "Command line pattern" box from this:
Hi all is there an equivalent fix for Simplicity Studio 5?
0
Hi @zageek,
Since you posted to thread, I assume you are running into this issue with Simplicity Studio 5 is that correct? Did you try the recommended solution with Simplicity Studio 5? I do not see any reason it would not work.
File Limit 32K Solution
I had previously asked a question about a problem I was having with the number of files in a project. At the time I had thought it was just a Simplicity v3.3 problem, and that upgrading to v4 had fixed it. Unfortunately, the problem quickly came back after a few more files were added.
It turns out this is an Eclipse CDT issue, specifically due to the 32K limit on the input of the CreateProcess function. At this time the issue remains unsolved.
The fix I've used is to write all the parameters to a file, and then read those in for the call to the linker. (The link step is where the problem is, as it tries to call gcc with all of the object code in a single command line). In Project->Properties->C/C++ Build->Settings->GNU ARM C Linker, I changed the "Command line pattern" box from this:
${COMMAND} ${FLAGS} ${OUTPUT_FLAG} ${OUTPUT_PREFIX} ${OUTPUT} ${INPUTS}
To this:
echo -E "${FLAGS} ${OUTPUT_FLAG} ${OUTPUT_PREFIX} ${OUTPUT} ${INPUTS}" > link.txt && ${COMMAND} @link.txt
This puts all the commands passed to the linker into a file, and then uses that as the input for the call.
Hi @bdionx,
Thank you for posting your solution!
Best Regards,
jpitt
Hi @zageek,
Since you posted to thread, I assume you are running into this issue with Simplicity Studio 5 is that correct? Did you try the recommended solution with Simplicity Studio 5? I do not see any reason it would not work.
Thank you,
jpitt