Can I display the output of a previous compile

Use case : after installing 3.0.2 and exCode 5.1.1, i got a storm of new warnings !!! mostly legit, cruft left over from early development stages refactorings. So i am on a rampage to remove these dreaded warnings. The specific app will be at its fifth AppStore publish, so i tend to do this on a line-by-line basis. So : fix a warning, compile, run unit test, run integrated test, and onwards. The compiler (after the fix) reports nada, since the only module modified now compiles warning-free. I would like to go back to the original 'full compile' output and carry on with the 60 or so modules i need to fix.

For the moment, i open a term, and touch a globally imported 'constants.h' file, and recompile.

Is there a builtin way i ignore to return to that full compile, to avoid the 45 seconds or so of wait for the compile to complete ?

ps. clean is not an option : 45 seconds turn into 200 seconds since compile occurs after the resources copy.

4 comments
Comment actions Permalink

Yves, there is no such an option at the moment, but thanks for the use case; here is a corresponding feature request.

0
Comment actions Permalink

haha ... ok.  I see you are still mulling over it.  I could suggest that the message tool window could have 'tabs', and a button to 'pin in a tab' a particular output log. I'll keep on touching and full-recompiling for now.

0
Comment actions Permalink

In this case it will be difficult to see the shole scope of problems at once. Ideally, the messages would only be updated for the recompiled files and the rest kept from the previous runs.

0
Comment actions Permalink

that would be a 'full' implementation  ... do it fast, do it better, do it well !!!  Possibly flag 'invalid' those warnings that have been corrected in the initial log. In the do it fast release, just the luser (me !!!) keep track of his doings. But of course, I am not the product manager :)

0

Please sign in to leave a comment.