This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
This issue "suddenly" appeared (in quotes for a reason).
I am fairly certain it is caused by a configuration issue.
It occurred when I was setting up the release build on a project (that was properly configured in debug but apparently not in release <sigh>).
Attempting to sync the settings between the 2 builds I tracked down what was in error with some thinking (they both needed to be the same model which apparently wasn't the case).. Anyhow I am fairly certain I set something on both configurations that inflicted this 'issue'.
It takes ~1 minute per .pp file for it to verify the file. Each of these files is < 10k in size. This should be almost instantaneous. The project has 23 such files so ... this could take a while. Nothing else in (such as compiling 76k size files) takes this long just the 'magic' pp files.
I'm a little confused as these files (pre-processor I assume) should be read before building object files? Why does it need to do ANYTHING with these after linking?
From the file time stamps the object files where generated in < 1 minute the .pp files (afterward?) took ~15 minutes and verifying those took ~20 minutes.
The output file was generated in < 2 minutes... prior to it iterating through the pp files, why is it "verifying" pp files etc if the output file is already generated?
It's not being run under a virtual machine so this is rather confusing. If I 'rectify' this I'll add a note as to what the cause is. Is their any way of knowing "what" it's doing (maybe why it's so slow). Anyhow suggestions welcome.
Sadly it changed nothing, however a clean build (or at least the generation of the code and linking) takes substantially less time than (whatever it is) the .pp dependency scan. It's quite strange behavior.
As I was creating a 'release' version for the program, might that have created issues (I've noticed that release copies nothing practically for the memory model etc from the debug when you attempt to create one).
Although thanks, I have nary found a way to rectify this. I will attempt next to create a new project and see if this behavior continues on a different project all together.
Stephen
AartiG said:Stephen,
As a first check, have you tried importing the same project into a new workspace and rebuilding? And does it consistently take the same amount of time each time you build the same project?
I "broke down" and reinstalled CCS5 complete, it appears it may have been a configuration issue or licensing issue. I fear having to "test" going from debug to release build again (sigh).
Anyhow thanks for your line of questioning, it gave me some ideas of what to look for. I also noted that uninstalling was almost impossible (kept complaining about things) so the whole install might have been "miffed". After re-installation things mostly work correctly. Lots of tires to re-kick.
Stephen