On Dec 27, 2011, at 5:10 PM, Joar Wingfors wrote: On 27 dec 2011, at 04:24, Andreas Grosam wrote: Whenever I make a change in the source, I have to wait a few minutes until the system goes idle before it makes sense to run the bench test and get reliable results. (for comparison: building takes few seconds).
I don't think that indexing should be be significantly slower than building. If this isn't the case for you, please file a bug report with reproducible set of steps / sample project, so that we can take a look.
Unfortunately, this kind of issue isn't reproducible in a trivial example project. But maybe the following info helps, too:
The project is part of a workspace which contains roughly 20 targets. Most of them are C++ products which includes a couple of headers from the boost library. A few targets build Objective-C products whose implementation depend on these C++ files. I understand that indexing heavy templetized source code - like the boost library - is comparable to a stress test for hard and software ;)
So, when I change a source file (say a header file) which has a lot of dependent files, indexing starts and the activity pane says for example "Indexing | Processed 1 of 73 files". When building a target it says "my_product | Compiling 1 of 6 source files…".
Indexing takes roughly 10 times longer than compiling.
Does this sound interpretable? (if not, my project becomes available soon as open source and you can take a look at it)
Would it be possible to interrupt indexing when a program is launched from within Xcode? (that way, wall-time of the execution time may become more reliable).
Andreas |