[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-devel
Subject:    Re: moc files
From:       "W. Tasin" <tasin () fhm ! edu>
Date:       2001-08-05 16:20:19
[Download RAW message or body]

Matthias Hoelzer-Kluepfel wrote:

> Hi all,
> 
> I am a bit tired to fix the moc includes in kdevelop every
> other day. Could we please agree to do it like all the other
> KDE programs, that is to include the .moc file in the cpp
> files? There is a script "kdesdk/scripts/includemocs" that
> helps to convert old code that linked to a .moc.o instead.
> 
> Thanks,
> Matthias.
> 
Hi,

could someone help me understand, why this is the actual method handling 
with moc files?

I know I'm a little bit outdated with being "state-of-the-art", but the 
only thing I found about the 2 methods adding moc files to the project 
is http://doc.trolltech.com/moc.html and there is written:

*Method A: The class declaration is found in a header (.h) file*
(the Makefile-method)
and
*Method B: The class declaration is found in an implementation ( .cpp) file*
(the #include-method)

So can someone give me an explanation to this new method to handle mocs?

Ciao

Walter

-- 
  The KDevelop project: tasin@kdevelop.de - http://www.kdevelop.org
--
oohhh sveglia.... il mondo e' ammalato, ma x colpa di chi.........
(Zucchero)
> -------W. Tasin, FB 04,FHM-------------------PGP-KeyID:0x7961A645---------:
<Key-Fingerprint: 1610 835F 0080 32F4 6140  6CF7 A7D0 44CD 7961A645>
<http://wwwkeys.pgp.net:11371/pks/lookup?op=index&search=0x7961A645&fingerprint=on>




-
to unsubscribe from this list send an email to kdevelop-devel-request@kdevelop.org \
with the following body: unsubscribe »your-email-address«


[prev in list] [next in list] [prev in thread] [next in thread]