Hello,
I face similar problems (see below) and looking for a solution, I got here. Alright, I can confirm the proposed workaround, disconnecting from the network definitely helps.
There may be another solution for those users, which use Windows and the External Builder in Eclipse, i.e., if Eclipse's hammer icon starts a makefile (or nmake, etc.) as an external process). In this case, it may help to use another set of UNIX tools (i.e., echo.exe, rm.exe, mkdir.exe, etc.) In my builds, I saw the slowdown in executing these commands. Particularly at the beginning, when mkdir creates the folders for the binary artifacts (or checks their presence) it was incredible slow, several seconds per folder. Not using mkdir.exe (and the others) from the S32DS installation (which happens by default) solved the problem.
Since I run the External Builder I can control the behavior by setting the environment accordingly and before I startup Eclipse. The external process sees the other set of commands in the Windows search path variable PATH before the IDE paths show up. The other involved tools, in particular the compiler, seems to be not affected by the problem.
What remains, and what I was actually looking for, is another aspect of the problem. While my build is alright, I still have the same issue with the startup of the debugger (GDB with P&E Multilink for PowerPC, JTAG). It's working without any error or perceivable failure, warning, etc. but it takes several minutes to enter the debug session. During this time, the progress bar is frozen at 61%. Once it progresses again, it takes just three seconds to reach 100%.
The "solution" is the same: Disconnecting the network. If you do it in "frozen" state then it takes another 5s to progress. If you click on the bug with disconnected network then it takes just a few seconds at all to enter the session.
Is there anything I can do, like configuring the firewall or similar?
Kind regards,
Peter
