PDA

View Full Version : "Nothing to be done for `first'" message when 'make' qwt



HYKim
28th January 2016, 11:09
Hi, I want to use qwt library.

I followed the instruction at http://qwt.sourceforge.net/qwtinstall.html

But when I typed 'make', I got some error message:




me@com:~/qwt-6.1.2$ make
cd src/ && ( test -e Makefile || /home/me/Qt5.5.1/5.5/gcc_64/bin/qmake /home/me/qwt-6.1.2/src/src.pro -spec linux-g++ -o Makefile ) && make -f Makefile
make[1]: Entering directory `/home/me/qwt-6.1.2/src'
compiling qwt_abstract_scale_draw.cpp
compiling qwt_clipper.cpp
.
.
.
moc qwt_wheel.h
compiling moc/moc_qwt_wheel.cpp
rm -f libqwt.so.6.1.2 libqwt.so libqwt.so.6 libqwt.so.6.1
linking ../lib/libqwt.so.6.1.2
ln -s libqwt.so.6.1.2 libqwt.so
ln -s libqwt.so.6.1.2 libqwt.so.6
ln -s libqwt.so.6.1.2 libqwt.so.6.1
rm -f ../lib/libqwt.so.6.1.2
mv -f libqwt.so.6.1.2 ../lib/
rm -f ../lib/libqwt.so
rm -f ../lib/libqwt.so.6
rm -f ../lib/libqwt.so.6.1
mv -f libqwt.so ../lib/
mv -f libqwt.so.6 ../lib/
mv -f libqwt.so.6.1 ../lib/
make[1]: Leaving directory `/home/me/qwt-6.1.2/src'
cd textengines/ && ( test -e Makefile || /home/me/Qt5.5.1/5.5/gcc_64/bin/qmake /home/me/qwt-6.1.2/textengines/textengines.pro -spec linux-g++ -o Makefile ) && make -f Makefile
make[1]: Entering directory `/home/me/qwt-6.1.2/textengines'
make[1]: Nothing to be done for `first'.
make[1]: Leaving directory `/home/me/qwt-6.1.2/textengines'
cd doc/ && ( test -e Makefile || /home/me/Qt5.5.1/5.5/gcc_64/bin/qmake /home/me/qwt-6.1.2/doc/doc.pro -spec linux-g++ -o Makefile ) && make -f Makefile
make[1]: Entering directory `/home/me/qwt-6.1.2/doc'
make[1]: Nothing to be done for `first'.
make[1]: Leaving directory `/home/me/qwt-6.1.2/doc'
cd designer/ && ( test -e Makefile || /home/me/Qt5.5.1/5.5/gcc_64/bin/qmake /home/me/qwt-6.1.2/designer/designer.pro -spec linux-g++ -o Makefile ) && make -f Makefile
make[1]: Entering directory `/home/me/qwt-6.1.2/designer'
compiling qwt_designer_plugin.cpp
In file included from qwt_designer_plugin.h:13:0,
from qwt_designer_plugin.cpp:23:
../../Qt5.5.1/5.5/gcc_64/include/QtDesigner/QDesignerCustomWidgetInterface:4:4: warning: #warning Header <QtDesigner/QDesignerCustomWidgetInterface> is deprecated. Please include <QtUiPlugin/QDesignerCustomWidgetInterface> instead. [-Wcpp]
# warning Header <QtDesigner/QDesignerCustomWidgetInterface> is deprecated. Please include <QtUiPlugin/QDesignerCustomWidgetInterface> instead.
^
compiling qwt_designer_plotdialog.cpp
rcc qwt_designer_plugin.qrc
compiling resources/qrc_qwt_designer_plugin.cpp
moc qwt_designer_plugin.h
compiling moc/moc_qwt_designer_plugin.cpp
In file included from moc/../qwt_designer_plugin.h:13:0,
from moc/moc_qwt_designer_plugin.cpp:9:
../../Qt5.5.1/5.5/gcc_64/include/QtDesigner/QDesignerCustomWidgetInterface:4:4: warning: #warning Header <QtDesigner/QDesignerCustomWidgetInterface> is deprecated. Please include <QtUiPlugin/QDesignerCustomWidgetInterface> instead. [-Wcpp]
# warning Header <QtDesigner/QDesignerCustomWidgetInterface> is deprecated. Please include <QtUiPlugin/QDesignerCustomWidgetInterface> instead.
^
moc qwt_designer_plotdialog.h
compiling moc/moc_qwt_designer_plotdialog.cpp
rm -f libqwt_designer_plugin.so
linking plugins/designer/libqwt_designer_plugin.so
mv -f libqwt_designer_plugin.so plugins/designer/
make[1]: Leaving directory `/home/me/qwt-6.1.2/designer'




I cannot understand why this result appear.
I would appreciate any kind of help.

Uwe
28th January 2016, 17:57
Not sure what you worry about - the build looks perfectly fine ?

The warnings about "QtDesigner/QDesignerCustomWidgetInterface" being deprecated indicates, that Qwt uses an include path, that is going to be changed in a future version of Qt. As long as we don't have this version this not important and if it happens some day there will be an update of Qwt, with a version depending include path.

"Nothing to be done for `first'.", means, that there is nothing to do in a directory for a specific make target ( here "first" ) - also nothing wrong with it. F.e. in the doc directory there is no build rule ( as there is nothing to build ), but there is an install rules, when calling "make install"

Uwe