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?
It's the normal behavior.
In the future, we have the plan to change the way Source Browser works but for the time being, either reduce the code size in your project or convert some part of code to libraries and link them, rather than compiling complete project at once.
Ah.
I hope it's soon. It's painful at the moment.
Back when I was actively using Visual Studio, and with systems with lots of source files to open and object/browse files to create, AV software profoundly interfered with build time performance. Hyperthreading slowed down Platform Builder. Back in the RealView days, licence management was also a big hog.
But I've seen this complaint about Keil quite often, someone needs to review the hashing and generation algorithms for these browse files.
I generally prefer SCI Tools Understand as a means to manage and navigate large projects, and IDE's with autocomplete and syntax checking I find more annoying than helpful, but to each their own.
Hello All,
Has this issue been resolved?
I have several projects I am working with lately; the main one - the largest - is very slow. I have turned off browse info.
I have two other smaller projects - same settings regarding the IDE - they compile very fast. I thought this was a AV thing based on some of the search results - but that's not it.
Thanks, John W.