(This applies to
Qt versions >= 4.7.3.) I made an attempt to build
Qt with custom parameters on my Debian box and it actually took AGES to compile (IIRC more than 6 hours on a single-core CPU). That's why I wanted to make sure I won't make any stupid mistakes in the process. However, I chose to do a
make clean to get the
*.o files and other stuff cleaned up after successful linking. It seemed a bad idea! For I did a
make install just after that, and you won't believe it, the
make clean attempt caused everything to get recompiled after the cleanup process!
Though up to now, I've been thinking that
make clean does allow a neat installation even with all object files and related stuff removed. Obviously, with
Qt, things are different.
In the official documentation for
Qt 4.7 (cf. http://qt-project.org/doc/qt-4.7/install-x11.html), they did not even mention an optional
make clean in the sequence of commands. As I know now, for a good reason.
All the same, I can't call this "complying with standards" as I've already compiled hundreds of open-source apps, and NEVER did
make clean trigger any recompilation process nor remove anything that should be kept (unless there was a bug in there)