Is is just me, or is there a problem when compiling with the Output option to generate Browser Information?
If I compile without generating Browser Information, compile times are decent.
>>MDK-ARM Professional 5.22 >>Parallel build configuration enabled for 8 jobs. >>Virus checker set to ignore all KEIL folders and executables. >>Virus checker set to ignore all project folders. >>Decently fast machine >>I have read this page: www.keil.com/.../armcc_chr1359124200911.htm
It's a large project, and waiting has become frustrating even for incremental builds.
I like to use browser information as it makes life easier when navigating code. Eclipse does an amazing job of indexing the source files (outside of compile time) for this purpose. I wish uVision would be the same.
Is there anything I can do speed things up?
My team is also experiencing frustratingly long build times when browse information is enabled.
We also have a large project and use Keil 5.22. When building with browse information it takes around 3 minutes to compile. Without browse information it is 15 seconds.
A few Keil versions ago the build time was closer to 30 seconds with browse information. We would like to get back under the 30 second time frame. Any ideas?
I totally agree. I experience the exact same problems. Our project takes also >3min to build on an i7 with 8 parallel jobs. And the same project used to build in much less than a minute with an older release.
Moving part of the project in a library is not always an option. I would also like to see some improvement here.
Regards Daniel Gross
My team is functioning with browse information turned off. Compile times are much faster, but you have to use search instead of go to definition. Some of my team have decided this is too inconvenient and switched development environments to Visual Studio. They only use Keil when needed for debugging.