kde3.5 msvc2005 question
pikeman at pikeman.sytes.net
Thu May 10 16:19:27 CEST 2007
Thank you, I understand what you said below about the .ui files below now.
My problem is specific to this kaboutdialog.moc:
1) why OBJMOC = moc\kaboutdialog.moc was inserted?
2) why this line insist on generating .moc from .cpp?
moc\kaboutdialog.moc: $(MOC) kaboutdialog.cpp
$(MOC) kaboutdialog.cpp -o moc\kaboutdialog.moc
Is there anything special about the kaboutdialog.h and kaboutdialog.cpp
do you see it in your kdeui/Makefile or it is my specific problem?
Jaros?aw Staniek wrote:
> Pike Man said the following, On 2007-05-10 15:37:
>> kde3.5 question:
>> in kdeui, why does the following always show up in Makefile generated by
>> qmake? nothing special in the kdeui.pro file.
>> I have been looking all over the place to get rid of it but can't find it.
>> if moc generates from kaboutdialog.h then it is ok.
>> Why it is trying to generate a moc file from cpp, I am getting a 0 size
>> .moc file...
> Files like kshortcutdialog_advanced.cpp are generated by uic. Makefile lines
> like SRCMOC = moc\moc_kshortcutdialog_advanced.cpp ... are there generated by
> qmake because there is FORMS section in kdeui.pro:
> FORMS = \
> kshortcutdialog_advanced.ui \
> kshortcutdialog_simple.ui \
> As kdeui.pro contains the following external command:
> system( bash kmoc )
> ...so when you run
> cd kdeui/
> .. appropriate kdeui/moc/*.moc files should be created, but the code generated
> from .ui files still use moc_**.cpp notation, not *.moc.
> In short, .moc files are only used (and included by hand) if generated from .h
> files written by hand.
More information about the Kde-windows