id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
150	"MOC output on ""No relevant classes found"""	rudi		"This is a rather weird one, but I'm asking for your opinion on that...

When MOC processes a file without any ""mocable"" classes, it creates a zero-length output file. Unfortunately, if the target drive is on a NetWare server, the timestamp of such a zero-length file is not updated (which is not MOC's fault). Anyway, as a result of that MAKE will re-invoke MOC for those classes - even though nothing has changed - and then cause the empty MOC result to be compiled. Due to this the target will be re-linked, which can be quiet time consuming.

A simple workaround for that problem is to always write something into the MOC result files. A carriage return would be sufficient, however I'm wondering why they don't put the standard ""this is a MOC generated file blah blah"" comment header in...

"	defect	closed	minor	Qt Enhanced	Tools	Unknown	low	wontfix