On future removing set(CMAKE_AUTOMOC TRUE)
error shown was[1]
Is it not required for sure?

[1]http://pastebin.com/5FbgUBwA

On Thu, Jan 29, 2015 at 4:19 PM, anu mittal <anu22mit...@gmail.com> wrote:

> Hi,
> on removing the .moc include i got errors
> shown - http://pastebin.com/GLka3Jrc
> CMakeFiles/compoundviewer.dir/kalziumglwidget.cpp.o: In function
> `KalziumGLWidget::KalziumGLWidget(QWidget*)':
> kalziumglwidget.cpp:(.text+0x35): undefined reference to `
> Avogadro::GLWidget::GLWidget(QWidget*)'
>
> mostly all says-undefined reference to `Avogadro::*'
>
> On Thu, Jan 29, 2015 at 3:27 PM, Thomas Baumgart <t...@net-bembel.de>
> wrote:
>
>> Hi,
>>
>> On Thursday 29 January 2015 15:07:42 anu mittal wrote:
>>
>> > I am working on the application Kalzium,the file kalziumglwidget.cpp
>> under
>> > it  includes the  #include "kalziumglwidget.moc" at the end of the code
>> and
>> > cmakefile has set(CMAKE_AUTOMOC TRUE) even after that on building it
>> shows-
>> >
>> > fatal error: kalziumglwidget.moc: No such file or directory
>> >  #include "kalziumglwidget.moc"
>> >                                ^
>> >
>> > what else do i need to take care of while working with .moc file?How can
>> > this be resolved?
>>
>> What happens if you simply remove this include statement? I think this
>> was the
>> solution I used a long time ago in a similar context.
>>
>> --
>>
>> Regards
>>
>> Thomas Baumgart
>>
>> GPG-FP: E55E D592 F45F 116B 8429   4F99 9C59 DB40 B75D D3BA
>> -------------------------------------------------------------
>> 'Debugging is twice as hard as writing the code in the first place.
>> Therefore, if you write the code as cleverly as possible, you are,
>> by definition, not smart enough to debug it.' - Brian W. Kernighan
>> -------------------------------------------------------------
>>
>>
>> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
>> unsubscribe <<
>>
>>
>
>
> --
> Regards,
> Anu.
>



-- 
Regards,
Anu.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Reply via email to