ESP32 Forum

Posted: **Thu Jul 05, 2018 5:38 pm**

Hello all,
I have an issue with Eclipse.
Everything was working fine but building time was a little bit slow. Quite normal under windows 10 and MSYS32.

For other reasons i tried activating WSL on windows. Since that moment, building under Eclipse didn't work. So i disabled WSL and now building works again. I did many things so not 100% sure it was the problem.
Problem is, it's now extremly slow. I tried building the helloworld through Eclipse and i'm at 11 minutes and it still at 31% !!

If i do this in MSYS32, i build in approx 1 minute and a half with a -j4. Still a long time for a simple example but this is consistent with what i had before in eclipse.
Any idea how i could have messed up my Eclipse build time ? and what i should do to correct this?

Posted: **Fri Jul 06, 2018 11:18 am**

If i run the python script in MSYS32, i also have a very long build time (more than hour).
So this is not related to eclipse.
Any idea?

Posted: **Mon Jul 09, 2018 6:44 am**

I had a similar issue in the past and it was caused by an antivirus/antimalware intensively checking files created during compilation.
Try disabling any antivirus/antimalware software or create an exception on the compilation folder.

Posted: **Tue Jul 10, 2018 10:16 pm**

FYI these are the instructions I use on MS WIndows developer machines to speedup the make:

Code: Select all

###
### IMPROVE MAKE's PERFORMANCE*** WINDOWS DEFENDER: DISABLE CHECKING THE MSYS2 FOLDER and MYIOT FOLDER
Windows Defender => Virus & Thread Protection => Virus & Thread protection settings => Exclusions:
	EXCLUDE DIR c:\msys32\
	EXCLUDE DIR c:\myiot\
	
###
### PROBLEM FIXING FIX for error ""error: cannot fork() for fetch-pack: Resource temporarily unavailable"" when doing Git push issues
#GITCMD>
\msys32\autorebase.bat

Posted: **Fri Jul 27, 2018 7:20 am**

mark;
Does anyone have resolved this problem?

Posted: **Fri Jul 27, 2018 3:16 pm**

Disable windows Defender from scanning your dev directory. (i.e. the build directory creates tons of files to scan). When using make, you can specify how many threads with -j option. So if you have a quad core w/ 2 threads per core then use 8.

make -j8

John A

Posted: **Fri Jul 27, 2018 3:41 pm**

I am using CMake IDF and average fresh compilation of very large project takes no longer than 10s and less than 20s with flashing.
It is like 2-3s after first compilation

We should all switch to CMake

ESP32 Forum

Extremely slwo build time in eclipse (not in MSYS)

Extremely slwo build time in eclipse (not in MSYS)

Re: Extremely slwo build time in eclipse (not in MSYS)

Re: Extremely slwo build time in eclipse (not in MSYS)

Re: Extremely slwo build time in eclipse (not in MSYS)

Re: Extremely slwo build time in eclipse (not in MSYS)

Re: Extremely slwo build time in eclipse (not in MSYS)

Re: Extremely slwo build time in eclipse (not in MSYS)