build/release takes forever (freedom_bootloader)

[roymessinger]

I've tried in various computers with KDS 3.2.0, all Win7. One of them with 32GB of RAM (Intel Xeon, E5-2620 - a heavy load computer). All of them takes to build this project a few minutes to 20 minutes (i see in the console each file is being built one after the other, and it takes time..).

Only in one computer (my private desktop with 32GB, SSD as hard drive, WIN 8.1) it takes few seconds, and the file is being built in super fast speed.

Any idea how come? it cannot be the SSD is the reason for that. The difference in the time is amazing.

Roy

[jasonscott]

Kaspersky was a huge drain on the compile times, i disabled it and it takes seconds as to a half hour.

[marceli1]

I recommend change OS to Windows10, which is much faster.

[bobpaddock]

Directories that do not exist and are in the PATH can slow GCC to a crawl.

There was a similar thread posted about slow compile times last fall, may find something helpful in that one.

[roymessinger]

Since the projects in all computers are exactly the same, the virus scanner seems a pretty good place to start.

Thanks for that.

I did not understand the directories which do not exist, though. How/where do I see these references to those directories?

[BlackNight]

It is basically your system PATH (on Windows). You can check it here (Window > Preferences):

They are inherited for the settings in the Project:

So when it launches the compiler, it will use that PATH for locating the binaries.

There is another setting where you could specify a custom path to your toolchain here:

I keep this empty (by default) so it uses the compiler found in PATH above.

I hope this helps,

Erich

[roymessinger]

My build variables are empty. Is this ok?

[BlackNight]

Have you checked 'show system variables'?

[roymessinger]

Silly me :smileyhappy:

It's still very very slow. Probably the anti virus. Thanks.

[BlackNight · Accepted solution]

Roy,

I have seen some virus scanner slowing down things by a factor of 10-20.

And: Can you check your PATH settings? maybe there is something in it to reach out on remote network drives?

Erich