nolden at kde.org
Sun Aug 5 23:37:43 UTC 2001
On Sunday, 5. August 2001 20:31, you wrote:
> first of all: after I've downloaded the changes of Matthias there were
> still some contradictions with the moc file includes. But this time my
> Makefiles were responsible for that. Therefore I changed them by hand :-|.
> Hmmm, maybe other people have "wrong" Makefiles, too and get into troubles
> when compiling. Is there a chance to get the "right" Makefiles into CVS? (
> I don't know if they are there already, but if, why did I have the "wrong
make -f admin/Makefile.common cvs-clean is your friend - as long as you don't
have uncommited files in your directory - mind that those will be deleted so
please do a backup before :) Then run the whole build-process and you should
be done. There's a macro in every Makefile.am that tells which headers to
produce moc.cpp and which ones are .moc files. The macro gets expanded into
the Makefile.in and Makefile to the rules that apply on the individual files.
> > could someone help me understand, why this is the actual method handling
> > with moc files?
> > *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)
> As mentioned there are two methods: the first one compiles the moc(.cpp)
> files and the cpp files separated and the second one includes the moc file
> into the matching cpp file and compiles only the cpp files. And not the moc
> files und cpp files separated.
> to unsubscribe from this list send an email to
> kdevelop-devel-request at kdevelop.org with the following body: unsubscribe
We're not a company, we just produce better code at less costs.
nolden at kde.org
The K Desktop Environment The KDevelop Project
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
More information about the KDevelop-devel