RFC: new way to handle MOC files ?

[Arnold Krille]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 21 February 2003 20:55, Michael Schuerig wrote:
> On Friday 21 February 2003 18:51, Alexander Neundorf wrote:
> > It works the following way: a moc file is required if a source or
> > header contains the Q_OBJECT macro. The create_global_moc script
> > parses all files given on its command line and searches checks which
> > files contain "Q_OBJECT". These files are remembered (e.g. foo.cpp)
> > and a new file "mocs.cpp" is created which will include all required
> > moc files (e.g. foo.cpp.moc).
> This means all moc files have to be recompiled when any header/source
> containing Q_OBJECT changes. Is that a good idea?

This is surely not a good idea!!! I am always thinking how to fasten the 
make-process but this is very bad...

Just remember the --enable-final is similar, we shouldn't mix between normal 
and final-mode...

Just my little opinion...

Arnold
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.5 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+WfHyr3oYC7XCTmIRAkg/AKCtL02Ukscak/ohUH8PFsc83MvMIgCeIx7z
WZIfHNEkS4qFZD0KkxGRTLs=
=F/vQ
-----END PGP SIGNATURE-----